Re: [Lilypond-auto] Patchy email

2012-08-26 Thread James
John, On 26 August 2012 11:39, John Mandereau wrote: > Hi James, >> 09:24:02 (UTC) Begin LilyPond compile, previous commit at >> d14e4770b85b3cacc647e45b9ebfe59cc085753f >> 09:24:07 Merged staging, now at: >> d14e4770b85b3cacc647e45b9ebfe59cc085753f >> 09:24:08Success:

Re: [Lilypond-auto] Patchy email

2012-08-26 Thread John Mandereau
Hi James, > 09:24:02 (UTC) Begin LilyPond compile, previous commit at > d14e4770b85b3cacc647e45b9ebfe59cc085753f > 09:24:07 Merged staging, now at: > d14e4770b85b3cacc647e45b9ebfe59cc085753f > 09:24:08Success:./autogen.sh --noconfigure > 09:24:18Succes

Re: [Lilypond-auto] Patchy email

2012-07-18 Thread David Kastrup
Graham Percival writes: > On Wed, Jul 18, 2012 at 01:58:54PM +0200, David Kastrup wrote: >> John Mandereau writes: >> >> > Sorry for bearing with my move to a more disciplined developer from a >> > hybrid of pyromaniac and fireman of the build system I used to be :-P >> >> It's not really triv

Re: [Lilypond-auto] Patchy email

2012-07-18 Thread Graham Percival
On Wed, Jul 18, 2012 at 01:58:54PM +0200, David Kastrup wrote: > John Mandereau writes: > > > Sorry for bearing with my move to a more disciplined developer from a > > hybrid of pyromaniac and fireman of the build system I used to be :-P > > It's not really trivial to get into LilyPond developme

Re: [Lilypond-auto] Patchy email

2012-07-18 Thread David Kastrup
John Mandereau writes: > Il giorno mer, 18/07/2012 alle 09.27 +0200, David Kastrup ha scritto: >> Well, now the accumulated mess in master is final, anyway. I have >> bumped staging to match it, so nothing is blocked anymore. I am not >> really interested in checking the consistency of all that

Re: [Lilypond-auto] Patchy email

2012-07-18 Thread John Mandereau
Il giorno mer, 18/07/2012 alle 09.27 +0200, David Kastrup ha scritto: > Well, now the accumulated mess in master is final, anyway. I have > bumped staging to match it, so nothing is blocked anymore. I am not > really interested in checking the consistency of all that since it > consists of manual

Re: [Lilypond-auto] Patchy email

2012-07-18 Thread David Kastrup
John Mandereau writes: > Il giorno mer, 18/07/2012 alle 00.52 +0200, David Kastrup ha scritto: >> The whole purpose of staging is that changes that should not get into >> master get _caught_ before they move into master (which is permanent). >> If you put "fixes" on _top_ of something bad in stag

Re: [Lilypond-auto] Patchy email

2012-07-17 Thread John Mandereau
Il giorno mar, 17/07/2012 alle 22.13 +0200, David Kastrup ha scritto: > It is not quite clear to me how the bug went through my tests, and why > Patchy does not complain (apparently make doc does not compile the "new" > snippets ?!?). Not every change to every source file is checked by Patchy. In

Re: [Lilypond-auto] Patchy email

2012-07-17 Thread John Mandereau
Il giorno mer, 18/07/2012 alle 00.52 +0200, David Kastrup ha scritto: > The whole purpose of staging is that changes that should not get into > master get _caught_ before they move into master (which is permanent). > If you put "fixes" on _top_ of something bad in staging, the whole mess > _will_ m

Re: [Lilypond-auto] Patchy email

2012-07-17 Thread David Kastrup
David Kastrup writes: > David Kastrup writes: > >> David Kastrup writes: >> >>> Please _don't_ ever push a "fix" on top of a broken staging branch. We >>> want to keep master compiling always. If your fix works, it means that >>> Patchy will move both the broken commit as well as the fix to m

Re: [Lilypond-auto] Patchy email

2012-07-17 Thread David Kastrup
David Kastrup writes: > David Kastrup writes: > >> Please _don't_ ever push a "fix" on top of a broken staging branch. We >> want to keep master compiling always. If your fix works, it means that >> Patchy will move both the broken commit as well as the fix to master. >> >> I've cleared both f

Re: [Lilypond-auto] Patchy email

2012-07-17 Thread David Kastrup
David Kastrup writes: > Please _don't_ ever push a "fix" on top of a broken staging branch. We > want to keep master compiling always. If your fix works, it means that > Patchy will move both the broken commit as well as the fix to master. > > I've cleared both for now and hope that no Patchy h

Re: [Lilypond-auto] Patchy email

2012-07-17 Thread David Kastrup
John Mandereau writes: > Hi David, > Il giorno mar, 17/07/2012 alle 20.19 +0200, lilypond-a...@mandereau.net > ha scritto: >> 18:02:01 (UTC) Begin LilyPond compile, previous commit at >> 7d195ce54c3fd467a1434d5399930d6610327e69 >> >> 18:02:51 Merged staging, now at: >> f22c889b1389cb7d761580762f

Re: [Lilypond-auto] Patchy email

2012-07-17 Thread John Mandereau
Hi David, Il giorno mar, 17/07/2012 alle 20.19 +0200, lilypond-a...@mandereau.net ha scritto: > 18:02:01 (UTC) Begin LilyPond compile, previous commit at > 7d195ce54c3fd467a1434d5399930d6610327e69 > > 18:02:51 Merged staging, now at: f22c889b1389cb7d761580762fe77973780f2f86 > > 18:02:52

Re: [Lilypond-auto] Patchy email

2012-05-24 Thread John Mandereau
Il giorno gio, 24/05/2012 alle 18.28 +0200, lilypond-a...@mandereau.net ha scritto: > 16:28:01 Begin LilyPond compile, commit: > bd3c92cbe6edabb9a006ff76290012aa8f8ed13a > > 16:28:03 *** FAILED STEP *** > > merge from staging > > maybe somebody pushed a commit directly to maste