Am Mittwoch, 14. Juli 2010, um 08:47:17 schrieb David Kastrup: > Graham Percival <gra...@percival-music.ca> writes: > > But if you're working on a separate branch (as is right and proper > > for a major change), then I'm not certain how to go about it. I'm > > looking forward to opinions. > > I don't see a problem here. Just merge origin/master into your work > branch occasionally, then the patch will be relative to the current > version.
The problem is that many regtest files and mainly documentation files contain \version "2.13.x" These lines will all be out of date if a release happened while the patch was under review. And in particular for new features, which require a particular version (i.e. a new feature, or a changed syntax that needs a convert-ly rule), it is essential that the version number is really the first version where that syntax exists in the used form... Cheers, Reinhold -- ------------------------------------------------------------------ Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
