|
From: | lilypond |
Subject: | Re: Issue 2397 in lilypond: Tuplet number incorrectly placed when using additonal arriculations and/or abreak |
Date: | Mon, 19 Mar 2012 09:30:59 +0000 |
Updates: Labels: Patch-reviewComment #9 on issue 2397 by address@hidden: Tuplet number incorrectly placed when using additonal arriculations and/or abreak
http://code.google.com/p/lilypond/issues/detail?id=2397#c9Patchy the autobot says: LGTM. No visible regtest changes. Of course, this is a bit dissatisfactory for a patch with regtest. Perhaps we should push regtests with a focus on visual differences (rather than crashes or new features) to staging before the patch itself goes through testing? That way, the regtests would show differences when things are fixed, rather than only when they go bad again.
[Prev in Thread] | Current Thread | [Next in Thread] |