Hi Marc, Thanks for the quick response.
> I think that no response means "yes, submit a patch" in this case. > If you checked your changes and did not find any negative effects, > then submitting a patch is the best way to go IMHO. Okay. > The guidance/mentoring is great in principle, but it is way easier for > developers to comment on "official" patches during the review process. Fair enough. I'll move forward towards a patch, and ping the list if I git-stumble. Thanks, Kieren. ________________________________ Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
