On Wed, Jul 18, 2012 at 01:02:26AM +0200, Fr?d?ric Bron wrote: > I am not sure this email has been seen. > I have proposed a patch for issue 2563. > Cheers, > Fr?d?ric
I'm sorry about that Frederic. You're quite right, we didn't respond to your post to bug-lilypond. Send the patch to lilypond-dev. This is the correct thing to do. If you have already done that then I'm sorry, but you just have to wait for one of the devs to respond. Below, a bit more detail if you're interested, and for any future contributions of patches from outside the main dev community. I'm not sure, but I think our policy on patch handling might be under developement. In the documentation I find: http://lilypond.org/doc/v2.15/Documentation/contributor/commits-and-patches which explains the process for those with git push access. Not much use to you, I suspect. Here we mention a Patch Meister: http://lilypond.org/doc/v2.15/Documentation/contributor/issue-classification But on this page: http://lilypond.org/doc/v2.15/Documentation/contributor/meisters there is no mention of a Patch Meister. Looks like the position is vacant. Cheers, Colin. -- Colin Hall _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
