On 2016/05/30 15:29:42, panteck wrote:
Are you recommending that I close this issue, apply my patch to a
development
branch in git, and try again?
"apply my patch to a development branch in git" may be as easy as git checkout -b non-default-prop master git branch --set-upstream-to=origin/master Since there isn't a SourceForge issue yet, nobody really has taken action on the patch. So it's probably easiest to do that and start over. https://codereview.appspot.com/300840043/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
