Re: incorrect version number in convert-ly rule

[Mark Polesky]

Graham Percival wrote:
> The vertical space renaming uses
>   @rule ((2, 13, 36))
>
> but that should be 39.  Unfortunately, simply updating
> this value in python/convert-ly might cause problems when
> previously-updated files (now incorrectly tagged as .36)
> try to be updated to .39 again.
>
> I'm willing to handle all the manual version updating if
> nobody else wants to do it.

Huh?  I recently did two vertical space renamings.  The
first one was for the \paper variables with commit #ee6e07b,
on Sun 17 Oct 2010, when VERSION looked like this:

MAJOR_VERSION=2
MINOR_VERSION=13
PATCH_LEVEL=36
[...]
VERSION_DEVEL=2.13.35

So I put that in the (2, 13, 36) rule.

The second vertical space renaming was for the grob
properties with commit #7eb311a, Sat 13 Nov 2010, when
VERSION looked like this:

MAJOR_VERSION=2
MINOR_VERSION=13
PATCH_LEVEL=39
[...]
VERSION_DEVEL=2.13.38

So I put that in the (2, 13, 39) rule.  Did I do something
wrong?

- Mark