----- Original Message -----
From: "Kieren MacMillan" <kieren_macmil...@sympatico.ca>
To: "Lilypond-User Mailing List" <lilypond-u...@gnu.org>
Cc: "lilypond-devel" <lilypond-devel@gnu.org>
Sent: Saturday, November 28, 2015 3:27 PM
Subject: improving ottavation
Hello all,
I’d like to help improve ottavation-related issues in Lilypond, by fixing
current less-than-perfect behaviour, and adding some helpful syntactic
sugar.
I believe there are only three accepted issues currently in the tracker
(cf.
http://sourceforge.net/p/testlilyissues/issues/search/?q=ottavabracket),
so I’m not sure what my best course of action is. Should I submit each
fix/request as a new issue, and then try to fix it myself (with or without
help)?
Thanks,
Kieren.
There are a few more related to the ottava itself:
https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AAccepted+AND+ottava
I think you could tackle this two ways:
1) An issue at a time. If you're doing this, update the existing issue with
the patch (via git-cl) and any commentary. When you're done, set that issue
to Fixed.
2) All together. If this does not create an unreviewable humongous patch,
then create a new tracker (with git-cl) and reference the other issues.
When this patch is pushed, set all the issues to fixed, referencing this
one.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
