Comment #26 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
The last upload is based on current master, the current work is based on staging. Since staging has not been bounced to master for a few days, I am not really sure what the next upload should look like. Indeed, there are a _number_ of incremental commits with separate focus piling up in the feature branch.
Is there a chance to get Patchy feedback for a branch tip (dev/eventchord or whatever) rather than a "patch" for which the base to which is supposed to apply is a moving target?
_______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
