[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 1501 in lilypond: not_smart rules left in git
From: |
lilypond |
Subject: |
Issue 1501 in lilypond: not_smart rules left in git |
Date: |
Sat, 05 Feb 2011 04:08:05 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Other Priority-Critical Maintainability
New issue 1501 by percival.music.ca: not_smart rules left in git
http://code.google.com/p/lilypond/issues/detail?id=1501
We're not moving on with stable release plans until I can run convert-ly on
the entire git tree and have it automagically work on everything without
warnings.
A test:
BUILD_DIR=build scripts/auxiliar/update-with-convert-ly.sh &> foo.txt
reveals a few warnings:
1)
Processing `Documentation/learning/common-notation.itely'...
Applying conversion: 2.13.39, 2.13.40, 2.13.42, 2.13.44, 2.13.46,
Vertical spacing changes might affect user-defined contexts. Please refer
to the manual for details, and update manually.2.13.48
2)
Processing `input/regression/lyrics-tenor-clef.ly'...
Applying conversion: 2.12.3, 2.13.0, 2.13.1, 2.13.4, 2.13.10,
Not smart enough to convert minimum-Y-extent; vertical spacing no longer
depends on the Y-extent of a VerticalAxisGroup.
Somebody needs to go through these files (and others with the same
message), and either:
- update the syntax of any relevant input code, then increase the version
number
- increase the version number without changing any code, because of reason
X.
- Issue 1501 in lilypond: not_smart rules left in git,
lilypond <=