Re: Can't get a patch through because of weekly development releases.

2010-07-15 Thread Carl Sorensen
On 7/15/10 9:24 AM, "Carl Sorensen" wrote: > > I think that David's idea has some promise now. Create a new branch, with a > version that's unique to this branch. Do all the changes in files to the > new version. Get the patch reviewed (and get the reviewers to ignore the > custom version). >

Re: Optimizations for pure-height approximations. (issue1817045)

2010-07-15 Thread n . puttock
http://codereview.appspot.com/1817045/diff/1/2 File lily/axis-group-interface.cc (right): http://codereview.appspot.com/1817045/diff/1/2#newcode125 lily/axis-group-interface.cc:125: pure_height_cache = scm_c_make_hash_table (1000); This default size appears to be too big (at least for my poor co

Re: Can't get a patch through because of weekly development releases.

2010-07-15 Thread Carl Sorensen
On 7/15/10 12:54 PM, "Graham Percival" wrote: > On Thu, Jul 15, 2010 at 07:15:38PM +0200, David Kastrup wrote: >> Graham Percival writes: >> >>> On Thu, Jul 15, 2010 at 09:24:05AM -0600, Carl Sorensen wrote: I think that David's idea has some promise now. Create a new branch, wit

Re: annoying info issues

2010-07-15 Thread Graham Percival
On Thu, Jul 15, 2010 at 07:23:08PM +0200, Werner LEMBERG wrote: > > Currently, if I say > > info lilypond > > I'm forwarded to `lilypond-usage'. About a year ago, somebody yelled at me for changing "info lilypond" to be the Manuals node of lilypond-web. I didn't know (and didn't) care enough

Re: Can't get a patch through because of weekly development releases.

2010-07-15 Thread Graham Percival
On Thu, Jul 15, 2010 at 07:15:38PM +0200, David Kastrup wrote: > Graham Percival writes: > > > On Thu, Jul 15, 2010 at 09:24:05AM -0600, Carl Sorensen wrote: > >> > >> I think that David's idea has some promise now. Create a new branch, with > >> a > >> version that's unique to this branch. >

annoying info issues

2010-07-15 Thread Werner LEMBERG
Currently, if I say info lilypond I'm forwarded to `lilypond-usage'. If I say info LilyPond I'm forwarded to `lilypond-notation'. Is this really intentional? IMHO it's silly to get different targets depending on whether to use uppercase and/or lowercase letters. If possible, I would lik

Re: Can't get a patch through because of weekly development releases.

2010-07-15 Thread David Kastrup
Graham Percival writes: > On Thu, Jul 15, 2010 at 09:24:05AM -0600, Carl Sorensen wrote: >> >> I think that David's idea has some promise now. Create a new branch, with a >> version that's unique to this branch. > > \version "9.999.9" ? How is that unique to a particular branch? -- David Ka

Re: Can't get a patch through because of weekly development releases.

2010-07-15 Thread Graham Percival
On Thu, Jul 15, 2010 at 09:24:05AM -0600, Carl Sorensen wrote: > > I think that David's idea has some promise now. Create a new branch, with a > version that's unique to this branch. \version "9.999.9" ? > When the patch is reviewed, and everything is ready to push, do some sort of > git grep

Re: Can't get a patch through because of weekly development releases.

2010-07-15 Thread Carl Sorensen
On 7/15/10 8:41 AM, "Graham Percival" wrote: > On Thu, Jul 15, 2010 at 02:45:41PM +0200, David Kastrup wrote: >> Graham Percival writes: > For the record, I'd call the shell script 15 minutes (Carl already > posted the commands, but I suspect it can be done in a "cleaner" > manner with reba

Re: Can't get a patch through because of weekly development releases.

2010-07-15 Thread Carl Sorensen
On 7/15/10 6:45 AM, "David Kastrup" wrote: > Graham Percival writes: > >> On Wed, Jul 14, 2010 at 08:56:25PM +0200, David Kastrup wrote: >>> Carl Sorensen writes: >>> The version number of a build from the current git will be higher than the last release version. This particular

Re: Can't get a patch through because of weekly development releases.

2010-07-15 Thread Graham Percival
On Thu, Jul 15, 2010 at 02:45:41PM +0200, David Kastrup wrote: > Graham Percival writes: > > > I think that writing a 5-10 line shell script for easily updating > > version numbers in a patch/commit would be much less work than > > checking all the above, though. > > The idea was to create a sch

Re: Can't get a patch through because of weekly development releases.

2010-07-15 Thread David Kastrup
Graham Percival writes: > On Wed, Jul 14, 2010 at 08:56:25PM +0200, David Kastrup wrote: >> Carl Sorensen writes: >> >> > The version number of a build from the current git will be higher than >> > the last release version. This particular patch uses changes in .cc >> > code, so it needs to be

Re: Can't get a patch through because of weekly development releases.

2010-07-15 Thread Graham Percival
On Wed, Jul 14, 2010 at 08:56:25PM +0200, David Kastrup wrote: > Carl Sorensen writes: > > > The version number of a build from the current git will be higher than > > the last release version. This particular patch uses changes in .cc > > code, so it needs to be rebuilt, and hence will always b

Re: Fault in split-line references

2010-07-15 Thread Graham Percival
On Thu, Jul 15, 2010 at 09:04:30AM +0100, Trevor Daniels wrote: > While checking the recent changes I made to the Learning > Manual I noticed the following fault in rendering texinfo > to html. I don't remember it being mentioned before, I've mentioned it, but I could never remember whether the p

Fault in split-line references

2010-07-15 Thread Trevor Daniels
While checking the recent changes I made to the Learning Manual I noticed the following fault in rendering texinfo to html. I don't remember it being mentioned before, and I can't see a reference to it in the Contributors Guide. When a cross-reference in a .itely file is split across two lines,