On Fri, Apr 27, 2012 at 11:14:23AM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Then we'll have hard numbers on which developers are abusing the
process. I mean, sure, we all know whose patches tend to be great
and whose patches tend to be problematic...
Graham Percival gra...@percival-music.ca writes:
On Fri, Apr 27, 2012 at 11:14:23AM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Then we'll have hard numbers on which developers are abusing the
process. I mean, sure, we all know whose patches tend to be
On Sat, Apr 28, 2012 at 10:13:50AM +0200, David Kastrup wrote:
In fact, if you have to
do half a dozen of iterations before getting things actually right on
the somewhat more than superficial level provided by our tests, you'll
have gained lots of good Karma on the road.
I was thinking that
Graham Percival gra...@percival-music.ca writes:
On Sat, Apr 28, 2012 at 10:13:50AM +0200, David Kastrup wrote:
In fact, if you have to
do half a dozen of iterations before getting things actually right on
the somewhat more than superficial level provided by our tests, you'll
have gained
On 28 April 2012 10:30, Graham Percival gra...@percival-music.ca wrote:
As long as I'm not personally playing nursemaid for people
who don't run the basic tests
It seems that the whole talk about running tests is only because of me not
running them before uploading my first patches because I
On 26 April 2012 20:41, Łukasz Czerwiński milimet...@gmail.com wrote:
Mike, Graham and David wrote about more or less automatic running of tests
and presenting only the results, possibly on an unused computer.
I realised that I have a server on Dreamhost that probably could be such a
Hello,
On 28 April 2012 23:18, Łukasz Czerwiński milimet...@gmail.com wrote:
On 28 April 2012 10:30, Graham Percival gra...@percival-music.ca wrote:
As long as I'm not personally playing nursemaid for people
who don't run the basic tests
It seems that the whole talk about running tests is
Hello,
How much CPU time and memory would regtests consume?
Depends on how many CPUs you can allocate. You can run reg tests on 1
CPU or xCPUs. You explicitly state the number in your make command
'make -j7 CPU_COUNT=7' test will use 7 CPUs
'make test' just uses 1 CPU (even if you have more
Łukasz Czerwiński milimet...@gmail.com writes:
On 28 April 2012 10:30, Graham Percival gra...@percival-music.ca
wrote:
As long as I'm not personally playing nursemaid for people
who don't run the basic tests
It seems that the whole talk about running tests is only because of me
- Original Message -
From: Łukasz Czerwiński
To: James
Cc: m...@apollinemike.com ; k-ohara5...@oco.net ; David Kastrup ;
lilypond-devel@gnu.org
Sent: Thursday, April 26, 2012 7:41 PM
Subject: Lilypond patchy and other Lilypond problems
Still requires 'someone' to 'do' something
Phil Holmes m...@philholmes.net writes:
OK. Regtest checking can mean three things. 1) Between releases,
comparing the output of the regtests with what they looked like before
and flagging any differences as potential problems. I do this. 2)
Doing the same thing for patches. Patchy does
On Fri, Apr 27, 2012 at 10:28:54AM +0200, David Kastrup wrote:
There is no reason whatsoever that this should only be done by a single
person.
Totally!
I would expect that _every_ person contributing more than two
patches per month should be able, after uploading a patch, to be running
Graham Percival gra...@percival-music.ca writes:
Then we'll have hard numbers on which developers are abusing the
process. I mean, sure, we all know whose patches tend to be great
and whose patches tend to be problematic... but a completely
automated, objective approach would remove any
Wooow, a lot of emails were posted in the last 24 hours :) I'll try to
comment all your important thoughts, but it's possible that I miss one or
two... Anyway:
On 26 April 2012 07:28, Graham Percival gra...@percival-music.ca wrote:
Some people encourage new contributors. I encourage new
Hello,
2012/4/26 Łukasz Czerwiński milimet...@gmail.com:
...
On 26 April 2012 09:05, James pkx1...@gmail.com wrote:
I've run patchy-test just now for the three patches outstanding this
morning. It's no a big deal, I've just never got round to running the
patchy-test scripts (well since
Hello,
On 26 April 2012 21:38, James pkx1...@gmail.com wrote:
No problem, but it doesn't mean that you can just do some code and
throw it up for review without ANY basic testing your side, it should
apply to current tree and it should also pass a basic 'make'.
Yes, before uploading a patch
Hello,
2012/4/26 Łukasz Czerwiński milimet...@gmail.com:
Well, LilyDev won't help me - on the server exists an already installed
system (Linux).
As for Virtualbox, I believe, that without having admin rights I can't
install it - correct me if I'm wrong.
Well I'm not a *NIX admin - I do
On Sat, Dec 13, 2008, Dan Eble d...@faithful.be said:
I have a hymnal that uses a single thick bar line at a mid-measure
line break that coincides with the end of a line of the poem.
I would have expected a hymnal to have been typeset, not engraved; far too
much work and lower profit in it
Reinhold Kainhofer wrote Saturday, December 13, 2008 2:14 AM
Am Samstag, 13. Dezember 2008 02:48:14 schrieb dem...@suffolk.lib.ny.us:
On Fri, Dec 12, 2008, Reinhold Kainhofer reinh...@kainhofer.com said:
Should we change \bar . to create a single
thick barline for reasons of consistency
Trevor Daniels wrote:
Reinhold Kainhofer wrote Saturday, December 13, 2008 2:14 AM
Am Samstag, 13. Dezember 2008 02:48:14 schrieb dem...@suffolk.lib.ny.us:
On Fri, Dec 12, 2008, Reinhold Kainhofer reinh...@kainhofer.com said:
Should we change \bar . to create a single
thick barline for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 13. Dezember 2008 13:26:46 schrieb Jonathan Kulp:
Trevor Daniels wrote:
I vaguely remember seeing such a dot used to separate the two parts of a
bar in compound time, much like the common dotted or dashed barline, but
I can't find
I have a hymnal that uses a single thick bar line at a mid-measure
line break that coincides with the end of a line of the poem.
It uses a double thick bar line at the end of a song.
Its repeat signs are four dots and a thick line (or two thick lines at
the end of a song). A bidirectional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 12. Dezember 2008 19:41:44 schrieb Galen Toews:
I cannot find how to produce a thick bar.
As far as I can seen in the code in bar-line.cc, there is currently no way to
create a single thick bar line. In compound barlines, a thick line
On Fri, Dec 12, 2008, Reinhold Kainhofer reinh...@kainhofer.com said:
Should we change \bar . to create a single
thick barline for reasons of consistency and instead add a new
bar line style \bar dot to create a single dot as a bar line?
newbies dumb Q - will the switch impact extant user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 13. Dezember 2008 02:48:14 schrieb dem...@suffolk.lib.ny.us:
On Fri, Dec 12, 2008, Reinhold Kainhofer reinh...@kainhofer.com said:
Should we change \bar . to create a single
thick barline for reasons of consistency and instead add a
Question to the other developers: Should we change \bar . to
create a single thick barline for reasons of consistency and instead
add a new bar line style \bar dot to create a single dot as a bar
line?
I don't object, but I've never seen a single thick barline in the
wild...
Werner
On 29-Jun-05, at 8:34 PM, Holtrop Sheila wrote:
There were two major problems in the Lilypond software for me in
engraving these piano pieces:
Problem 1: Slurs and ties cannot be properly implemented in many
cases. I have attached a small Lilypond file that demonstrates the
problems I have
To whom it may concern,
I was intrigued by Lilypond and the Mutopia project. As a sign of support I attempted to use Lilypond to engrave the following four Ragtime piano pieces: Magnetic Rag, Weeping Willow, Pineapple Rag, and Topliner Rag.
Unfortunately, using Lilypond I was unable to mimic
28 matches
Mail list logo
