Comment #4 on issue 1554 by percival.music.ca: update midi2ly version number
http://code.google.com/p/lilypond/issues/detail?id=1554
1) it causes confusion amongst users
2) if somebody is running midi2ly with version 2.12.3, then it's quite
possible that they'd use some constructs that aren't supported in 2.8, or
stuff whose syntax has changed between 2.7.38 and now (such as vertical
spacing). Then there might be confusion if somebody runs convert-ly.
Basically, if somebody knows that they're doing with \version numbers, then
they can change it themselves. Otherwise, I think that defaulting to the
last major stable version (2.12.0) will produce the least amount of angst.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
