On Sun, Sep 11, 2011 at 04:06:14PM +0100, Phil Holmes wrote: > Same problem as 2.15.9 - I think the change of spacing from the clef > to the first note means that almost every regtest is different. I > get the same problem on my pixel comparator. I can't go back to an > earlier version because of the clef change.
Hmm. I'll upload 2.15.11, containing comparisons against 2.15.10 and 2.15.9. The latter still shows tons of changes, so I don't know if it'll help at all. I was sorely tempted to call it a release candidate anyway, but in the end I figured that I should a few days. ... BTW, with your fancy shiny computer, you /might/ want to try the steps to regenerate regtests without a specific commit. First get your git repo into the state you want (i.e. release-2.15.9-1 but also reverting patch abcd1234), then follow these: http://lilypond.org/doc/v2.15/Documentation/contributor/release-extra-notes It won't be fun, but it's doable... and if you can make a regtest comparison without the change-everything commit(s) with an hour or two of fumbling around and recompiling stuff, you could save people an hour (or more) of manually comparison regtests. Cheers, - Graham _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
