[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: |
Fri, 27 Dec 2013 06:45:52 +0000 |
Comment #8 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
Adding the dummy rule is part of the release process.
As to the email discussion interpretation: running convert-ly unnecessarily
is cheap. And people using 2.18.1+ or 2.19.* will be running convert-ly
anyway.
People don't run the latest stable necessarily: that's why the LSR is
usually trailing at least one stable version behind. And it's impossible
to guess whether a given snippet in LilyPond can be moved into the LSR when
the LSR is moved forward, like from 2.14.x to 2.16.x as it will happen soon
(hopefully).
So if we want a sweep upwards of version numbers, it's better done
manually: latest stable is too fresh for a number of reasons.
--
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