"Phil Holmes" <[email protected]> writes: > ----- Original Message ----- > From: "David Kastrup" <[email protected]> > To: "Phil Holmes" <[email protected]> > Cc: <[email protected]> > Sent: Thursday, July 17, 2014 12:07 PM > Subject: Re: LSR updates > > >> Phil Holmes <[email protected]> writes: >> >>> I'm starting work on bringing the snippets in git up to date to match >>> those in the LSR. Stage one is to change the LSR address of dsi to di in >>> them all and to bring their version numbers up to 2.18.0. This >>> isn't best >>> done with makelsr because it does not blindly update sll the snippets, >>> which is what we want. >> >> Uh, why would we want this? convert-ly was changed _exactly_ because we >> don't want the version numbers to be updated blindly. > > > Running convert-ly as part of makelsr updated quite a lot, but not > all.
Which is as intended. > Given that the LSR is now at version 2.18, it seems best to put all > the snippets at a consistent version, using 2.18 commands. At the current point of time it is no longer possible to run makelsr without having all versions for which there is a Documentation/snippets/new getting reset to an earlier version. This precludes me from being able to push issue 3998. Also you failed to update the "Note: this file works from version x.xx.x" comments. The current situation is quite a mess. I don't understand why you could not be bothered to go through the regular procedure for an invasive change like that and provided just few hours of warning and no patch to review. I suggest that we revert the respective commit while it can be done reasonably cleanly and then proceed in a less helterskelter manner. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
