lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 3675 in lilypond: Patch: Make convert-ly -d on


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3675 in lilypond: Patch: Make convert-ly -d only ever update on changed files
Date: Sun, 01 Dec 2013 11:54:27 +0000

Updates:
        Status: Fixed
        Labels: -Type-Enhancement -Patch-push Type-Scripts Fixed_2_19_0

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

Pushed to staging as
commit 15b9d5a33fe02826075a651e96ae21d2ae66a680
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).


This is not necessarily the last piece of work: some option for explicitly setting a minimum version to use might make sense. However, this state is for now needed to work on stable/unstable branch in parallel without drawing lots of merge conflicts.

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]