Re: Plans for changing chord repeat implementations

2012-01-28 Thread David Kastrup
Nicolas Sceaux writes: > Le 26 janv. 2012 à 11:00, David Kastrup a écrit : > >> The bad news is that absolute pitch friends would have to call the \q >> function (any better name for it?) explicitly. Since q is an input >> convenience, and relative pitch is also an input convenience, I don't >>

Re: Patchy email

2012-01-28 Thread Graham Percival
On Sat, Jan 28, 2012 at 09:18:03AM -0500, Julien Rioux wrote: > I'll have to test again with -j3, sorry. I suggest we erase the last > two commits from staging until this is resolved. The convert-ly commit > should be pretty safe. oh, I did that an hour ago, and Patchy's finished merging it now.

Re: Patchy email

2012-01-28 Thread Julien Rioux
On Sat, Jan 28, 2012 at 9:14 AM, Graham Percival wrote: > On Sat, Jan 28, 2012 at 09:07:12AM -0500, Julien Rioux wrote: >> Thanks. Are there known issues about running multiple lilypond-book >> instances in parallel when they touch the same files? I'm guessing >> this is what's going on because a

Re: Patchy email

2012-01-28 Thread Graham Percival
On Sat, Jan 28, 2012 at 09:07:12AM -0500, Julien Rioux wrote: > Thanks. Are there known issues about running multiple lilypond-book > instances in parallel when they touch the same files? I'm guessing > this is what's going on because a lot of the test files input the same > snippets as example, wh

Re: Patchy email

2012-01-28 Thread Julien Rioux
On Sat, Jan 28, 2012 at 8:58 AM, James wrote: > Julien, > > On 28 January 2012 13:31, Julien Rioux wrote: >> On Sat, Jan 28, 2012 at 7:27 AM, Graham Percival >> wrote: >>> On Sat, Jan 28, 2012 at 04:18:00AM -0800, lilypond.patchy.gra...@gmail.com >>> wrote: *** FAILED BUILD ***  

Re: Patchy email

2012-01-28 Thread Graham Percival
On Sat, Jan 28, 2012 at 08:31:04AM -0500, Julien Rioux wrote: > On Sat, Jan 28, 2012 at 7:27 AM, Graham Percival > wrote: > > On Sat, Jan 28, 2012 at 04:18:00AM -0800, lilypond.patchy.gra...@gmail.com > > wrote: > > make[1]: *** [out-test/tex-fragment.tex] Error 1 > > make[1]: *** Waiting for unf

Re: Patchy email

2012-01-28 Thread James
Julien, On 28 January 2012 13:31, Julien Rioux wrote: > On Sat, Jan 28, 2012 at 7:27 AM, Graham Percival > wrote: >> On Sat, Jan 28, 2012 at 04:18:00AM -0800, lilypond.patchy.gra...@gmail.com >> wrote: >>> *** FAILED BUILD *** >>> >>>       nice make test -j3 CPU_COUNT=3 >>> >>>       Previous

Re: Patchy email

2012-01-28 Thread Julien Rioux
On Sat, Jan 28, 2012 at 7:27 AM, Graham Percival wrote: > On Sat, Jan 28, 2012 at 04:18:00AM -0800, lilypond.patchy.gra...@gmail.com > wrote: >> *** FAILED BUILD *** >> >>       nice make test -j3 CPU_COUNT=3 >> >>       Previous good commit:   05efb98f2e3ff68f4bb8221db640b0174bfcde93 >> >>      

updated git-cl

2012-01-28 Thread Graham Percival
there's an improved git-cl on my github account now: https://github.com/gperciva/git-cl Thanks to Lukasz Czerwinski, it tracks all lilypond patches with the same base url. http://codereview.appspot.com/search?base=http://git.savannah.gnu.org/gitweb/?p=lilypond.git/trunk/ All contributors are stil

Re: Patchy email

2012-01-28 Thread Graham Percival
On Sat, Jan 28, 2012 at 04:18:00AM -0800, lilypond.patchy.gra...@gmail.com wrote: > *** FAILED BUILD *** > > nice make test -j3 CPU_COUNT=3 > > Previous good commit: 05efb98f2e3ff68f4bb8221db640b0174bfcde93 > > Current broken commit: b445e1b4207996eee2362187fa3e8b8af8ff05ba

Patchy email

2012-01-28 Thread lilypond . patchy . graham
Begin LilyPond compile, commit: 05efb98f2e3ff68f4bb8221db640b0174bfcde93 Merged staging, now at: b445e1b4207996eee2362187fa3e8b8af8ff05ba Success:./autogen.sh --noconfigure Success:../configure --disable-optimising Success: