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

[lilypond]

Updates:
        Labels: Fixed_2_17_98

Comment #6 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

Backport or not?  If I backport, with the release of 2.18.0 all versions in  
the code base, the snippets, the regtests, the documentation and so on will  
get their version header bumped to 2.18.0.  I don't think that's desirable,  
at least not for the snippets.  For regtests and documentation, I don't see  
much of an advantage/disadvantage.  Having different behavior here would  
require changes to scripts/auxiliar/update-with-convert-ly.sh.  As long as  
that is not done, I think we are best off keeping stuff in stable/unstable  
synchronized for now, meaning that I cherry-pick this change into  
stable/2.18 as
commit c2c44ef555bb2eb890ff1647065968699a857722
Author: David Kastrup <address@hidden>
Date:   Mon Nov 25 00:59:55 2013 +0100

    Issue 3675: Make convert-ly -d only ever update on changed files

    Previously, it updated unconditionally whenever a new stable version
    came out, leading to merge conflicts.  When the final applied
    conversion is to an unstable version and the following stable version
    is not beyond the conversion target, the following stable version is
    used.

    Note that this rule does not make a factual difference for continuous
    updates of a code base (the normal use case for
    scripts/auxiliar/update-with-convert-ly.sh), but it makes a difference
    for the conversion/import of code that may have fallen behind a lot
    (like with the LSR import, or when converting archived files).



--
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