Graham Percival <gra...@percival-music.ca> writes:
> On Fri, Oct 28, 2011 at 04:49:26AM +0000, lilyp...@googlecode.com wrote:
>>
>> Oh, convert-ly _is_ clean. I am waiting for the version number to
>> bump (every minute now?) so that my convertrules.ly don't create
>> files with a later version than the current one.
>
> yes, any minute now. The upload will probably start in 10 minutes
> -- it's finished compiling stuff. My computer has a slow HD and
> GUB does 1 or 2 mirroring of ~1.0 gigs of docs and stuff. or
> maybe my computer has a fast HD and it's just struggling with all
> that stuff.
>
> incidently, I saw that I increased the version number properly
> after 2.15.15; all that's was missing is a new release.
PACKAGE_NAME=LilyPond
MAJOR_VERSION=2
MINOR_VERSION=15
PATCH_LEVEL=16
MY_PATCH_LEVEL=
VERSION_STABLE=2.14.2
VERSION_DEVEL=2.15.15
My python/convertrules.py aims for 2.15.17 however, as the
\makeStringTuning change is already committed:
@rule ((2, 15, 7),
_ ("Handling of non-automatic footnotes."))
--
@rule ((2, 15, 9),
_ ("Change in internal property for MultiMeasureRest"))
--
@rule ((2, 15, 10),
_ ("Creation of a Flag grob and moving of certain Stem properties to
this grob"))
--
@rule ((2, 15, 16), r"\makeStringTuning, \contextStringTuning -> \stringTuning")
def conv (str):
--
@rule ((2, 15, 17), "\\markuplines -> \\markuplist")
def conv (str):
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
