Re: [Lilypond-auto] Issue 3675 in lilypond: Patch: Make convert-ly -d only ever update on changed files

[lilypond]

Comment #7 on issue 3675 by address@hidden: Patch: Make convert-ly -d  
only ever update on changed files
http://code.google.com/p/lilypond/issues/detail?id=3675

Whether you backport or not, there will be no \version "2.18.0" written  
until we make a dummy rule for 2.18.0 in convertrules.py

My read of this patch is that it updates version-number on /fewer/ files.   
A regression test unchanged since 2.16.2 retains its \version 2.16.2 (which  
is possibly useful information).

My read of the email discussions was that we /do/ want the Snippets updated  
to the latest stable version, even if they still work with earlier  
versions, to save people the trouble of running convert-ly unnecessarily on  
Snippets they want to adopt.  The default convert-ly updates to the latest  
version whether there are changes or not, so regular users are likely to  
expect the latest version number in a file.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings