Re: Patchy email from PhilH

2012-10-06 Thread Phil Holmes
- Original Message - From: "John Mandereau" To: Cc: Sent: Saturday, October 06, 2012 3:13 AM Subject: Re: Patchy email from PhilH This email looks like you're using an old revision of Patchy; in case it doesn't include convenience/safety checks before pushing t

Re: Patchy email from PhilH

2012-10-05 Thread John Mandereau
Il giorno ven, 05/10/2012 alle 08.11 -0700, philehol...@googlemail.com ha scritto: > Begin LilyPond compile, commit: 4ed5d7710416aff0a9e68f0d751b4e15c30fdf92 > > Merged staging, now at: c9d806f28ab690c3f210e14153c6bd31d506588e > > Success:./autogen.sh --noconfigure >

Re: Patchy email from PhilH

2012-10-05 Thread David Kastrup
David Kastrup writes: \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) /media/IntelSSD/patchybuild/autobuild/build/out/lybook-db/61/lily-1564b6f0.ly:144:12: error: wrong type for argument 2. Expecting string or music, found ((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 .

Re: Patchy email from PhilH

2012-10-05 Thread David Kastrup
"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > To: > Sent: Friday, October 05, 2012 4:55 PM > Subject: Re: Patchy email from PhilH > > >> "Phil Holmes" writes: >> >>> - Original Messag

Re: Patchy email from PhilH

2012-10-05 Thread Phil Holmes
- Original Message - From: "David Kastrup" To: Sent: Friday, October 05, 2012 4:55 PM Subject: Re: Patchy email from PhilH "Phil Holmes" writes: - Original Message - From: To: Cc: Sent: Friday, October 05, 2012 4:11 PM Subject: Patchy email

Re: Patchy email from PhilH

2012-10-05 Thread David Kastrup
"Phil Holmes" writes: > - Original Message - > From: > To: > Cc: > Sent: Friday, October 05, 2012 4:11 PM > Subject: Patchy email from PhilH > > >> Begin LilyPond compile, commit: 4ed5d7710416aff0a9e68f0d751b4

Re: Patchy email from PhilH

2012-10-05 Thread Phil Holmes
- Original Message - From: To: Cc: Sent: Friday, October 05, 2012 4:11 PM Subject: Patchy email from PhilH Begin LilyPond compile, commit: 4ed5d7710416aff0a9e68f0d751b4e15c30fdf92 Merged staging, now at: c9d806f28ab690c3f210e14153c6bd31d506588e Success: ./autogen.sh --noconfigure

Patchy email from PhilH

2012-10-05 Thread phileholmes
Begin LilyPond compile, commit: 4ed5d7710416aff0a9e68f0d751b4e15c30fdf92 Merged staging, now at: c9d806f28ab690c3f210e14153c6bd31d506588e Success:./autogen.sh --noconfigure Success:../configure --disable-optimising Success:

Re: Patchy email from PhilH

2012-09-28 Thread David Kastrup
"Phil Holmes" writes: > I'm always a little nervous about simply deleting staging, although I > know this is the correct approach. David - could you give me the > commands needed to delete and recreate staging, please? (Private mail > if you don't want everyone to try this out). Everyone does

Re: Patchy email from PhilH

2012-09-28 Thread Phil Holmes
- Original Message - From: To: Cc: Sent: Friday, September 28, 2012 2:44 PM Subject: Patchy email from PhilH Begin LilyPond compile, commit: cd09a4e7f2655f3bec65979a604d8f9f9bf454da Merged staging, now at: 0d09cf7fd29ae8f746b58f4c6c3b97abee8ce8f7 Success: ./autogen.sh

Patchy email from PhilH

2012-09-28 Thread phileholmes
Begin LilyPond compile, commit: cd09a4e7f2655f3bec65979a604d8f9f9bf454da Merged staging, now at: 0d09cf7fd29ae8f746b58f4c6c3b97abee8ce8f7 Success:./autogen.sh --noconfigure Success:../configure --disable-optimising Success:

Patchy email from PhilH

2012-09-01 Thread phileholmes
Begin LilyPond compile, commit: ecf25f33aa4c02efda0694280e956c147f5006ae Merged staging, now at: 5a3e62fdcaa01c295f2c5a5d1d47f81752ac7e7f Success:./autogen.sh --noconfigure Success:../configure --disable-optimising Success:

Re: Patchy email from PhilH

2012-08-23 Thread Phil Holmes
Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: Sent: Thursday, August 23, 2012 4:34 PM Subject: Re: Patchy email from PhilH "Phil Holmes" writes: I'd not run it for a while, so yes. This was a result of my build machine turnin

Re: Patchy email from PhilH

2012-08-23 Thread David Kastrup
"Phil Holmes" writes: > I'd not run it for a while, so yes. This was a result of my build > machine turning off in the middle of a patchy run. Re-running it gave > this result, since it thought that a patchy run was in progress. > Re-running it again failed on the doc build, although it looked

Re: Patchy email from PhilH

2012-08-23 Thread Phil Holmes
- Original Message - From: "David Kastrup" To: Sent: Thursday, August 23, 2012 4:13 PM Subject: Re: Patchy email from PhilH philehol...@googlemail.com writes: Begin LilyPond compile, commit: a23befd66195ef6a83c1f99926597a83bd967e94 *** FAILED STEP *** merge from stag

Patchy email from PhilH

2012-08-23 Thread phileholmes
Begin LilyPond compile, commit: a23befd66195ef6a83c1f99926597a83bd967e94 *** FAILED STEP *** merge from staging maybe somebody pushed a commit directly to master? Begin LilyPond compile, commit: a23befd66195ef6a83c1f99926597a83bd967e94 Merged staging, now at: b512dbe4d29be6b450

Re: Patchy email from PhilH

2012-08-23 Thread David Kastrup
philehol...@googlemail.com writes: > Begin LilyPond compile, commit: a23befd66195ef6a83c1f99926597a83bd967e94 > > *** FAILED STEP *** > > merge from staging > > maybe somebody pushed a commit directly to master? Uh. commit a23befd66195ef6a83c1f99926597a83bd967e94 Author: Phil Holmes

Patchy email from PhilH

2012-08-23 Thread phileholmes
Begin LilyPond compile, commit: a23befd66195ef6a83c1f99926597a83bd967e94 *** FAILED STEP *** merge from staging maybe somebody pushed a commit directly to master? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gn