CG: explanation of branches for the impatient (issue 5484043)

2011-12-12 Thread graham
Reviewers: , Message: CG now has N+1 different introductory explanations of git, where N is at least 3. But given the lack of familiarity with branches that I see in our development community, and the new staging stuff, I think this one is good. Once it's been accepted (in whatever form), I'll

Release news, development news, state of the world

2011-12-12 Thread Graham Percival
Here's where we stand. STABLE RELEASE Almost everybody wants stable releases more frequently. They attract positive attention, they get updated docs and bugfixes and new features into the hands of users, etc. We had the first two release candidates back in Sep. Unfortunately, we've had Critic

Re: Release news, development news, state of the world

2011-12-12 Thread David Kastrup
Graham Percival writes: > STABLE RELEASE > > Almost everybody wants stable releases more frequently. They > attract positive attention, they get updated docs and bugfixes and > new features into the hands of users, etc. We had the first two > release candidates back in Sep. Unfortunately, we'v

Re: Allows for automatic renumbering of measure numbers at volta repeats. (issue 5440049)

2011-12-12 Thread n . puttock
On 2011/12/06 12:07:03, mike_apollinemike.com wrote: Good to see you back on the list! Cheers mate. :) I'm afraid I'm only passing through temporarily though. Hopefully will get back into the swing of things after Christmas. Cheers, Neil http://codereview.appspot.com/5440049/

Re: Adds parenthesized measure numbers at mid-bar breaks. (issue 5452057)

2011-12-12 Thread n . puttock
http://codereview.appspot.com/5452057/diff/7002/scm/define-context-properties.scm File scm/define-context-properties.scm (left): http://codereview.appspot.com/5452057/diff/7002/scm/define-context-properties.scm#oldcode127 scm/define-context-properties.scm:127: (barNumberVisibility ,procedure? "A

Re: Patchy email

2011-12-12 Thread Graham Percival
On Mon, Dec 12, 2011 at 04:22:59AM -0800, lilypond.patchy.gra...@gmail.com wrote: > *** FAILED BUILD *** > > nice make doc -j3 CPU_COUNT=3 > > Previous good commit: f8e03b152b436d6034dd17e71335fc6221497571 > > Current broken commit: 438084fc487d6e575500a4e2866ef750476ce6cf

Re: Release news, development news, state of the world

2011-12-12 Thread Colin Campbell
On 11-12-12 04:16 AM, David Kastrup wrote: Graham Percival writes: STABLE RELEASE Almost everybody wants stable releases more frequently. They attract positive attention, they get updated docs and bugfixes and new features into the hands of users, etc. We had the first two release candidate

Away for a few days

2011-12-12 Thread Phil Holmes
Folks, I'm away from home until Friday 16 December, staying in the Martello Tower in Aldeburgh (http://www.landmarktrust.org.uk/BuildingDetails/Overview/199/Martello_Tower#). I don't believe it has mobile phone coverage, broadband, TV or anything like that, so I won't be able to do anything b

Re: Release news, development news, state of the world

2011-12-12 Thread Graham Percival
On Mon, Dec 12, 2011 at 07:06:56AM -0700, Colin Campbell wrote: > FWIW, I've found that GUB on x86-64 Oneiric will choke building > cross-compiled components, with error messages saying "unable to > identify extension of x", where x is the x.o form of a tool. This > points, according to GCC, to m

Patchy email

2011-12-12 Thread lilypond . patchy . graham
Begin LilyPond compile, commit: aeda0cc2675a13ade10f3f97630ffa7dadd111aa Success:No new commits in staging Begin LilyPond compile, commit: aeda0cc2675a13ade10f3f97630ffa7dadd111aa Success:No new commits in staging Begin LilyPond compile, commit: a

Patchy email

2011-12-12 Thread lilypond . patchy . graham
Begin LilyPond compile, commit: f8e03b152b436d6034dd17e71335fc6221497571 Merged staging, now at: 438084fc487d6e575500a4e2866ef750476ce6cf Success:./autogen.sh --noconfigure Success:../configure --disable-optimising Success:

Re: Patchy email

2011-12-12 Thread m...@apollinemike.com
On Dec 12, 2011, at 1:22 PM, lilypond.patchy.gra...@gmail.com wrote: > Begin LilyPond compile, commit: f8e03b152b436d6034dd17e71335fc6221497571 > > Merged staging, now at: 438084fc487d6e575500a4e2866ef750476ce6cf > > Success:./autogen.sh --noconfigure > > Succe

Re: Patchy email

2011-12-12 Thread David Kastrup
lilypond.patchy.gra...@gmail.com writes: > Begin LilyPond compile, commit: aeda0cc2675a13ade10f3f97630ffa7dadd111aa > > Success:No new commits in staging > > Begin LilyPond compile, commit: aeda0cc2675a13ade10f3f97630ffa7dadd111aa > > Success:No ne

Re: Patchy email

2011-12-12 Thread Graham Percival
On Mon, Dec 12, 2011 at 04:52:41PM +0100, David Kastrup wrote: > lilypond.patchy.gra...@gmail.com writes: > > > *** FAILED STEP *** > > > > merge from staging > > > > maybe somebody pushed a commit directly to master? > > Nope. staging is strictly ahead of master. > > Lockfile problem o

Re: Patchy email

2011-12-12 Thread David Kastrup
Graham Percival writes: > On Mon, Dec 12, 2011 at 04:52:41PM +0100, David Kastrup wrote: >> lilypond.patchy.gra...@gmail.com writes: >> >> > *** FAILED STEP *** >> > >> >merge from staging >> > >> >maybe somebody pushed a commit directly to master? >> >> Nope. staging is strictly ahead

Re: CG: explanation of branches for the impatient (issue 5484043)

2011-12-12 Thread k-ohara5a5a
Looks fine, except for a couple `git merge` commands where I suggest other things. The closest analogue to applying patch files is not `git merge` but rather `git cherry-pick`. But that is not so useful as the analogue of creating a series of one or more patch files, and applying them in sequence