Janek Warchoł <janek.lilyp...@gmail.com> writes: > On Mon, Sep 3, 2012 at 1:00 PM, Graham Percival > <gra...@percival-music.ca> wrote: >> I think that any time that a LilyPond developer complains that >> the code is too hard to understand, the patch should automatically >> move to Patch-needs_work. Automatically. >> If there's a long discussion and there's overwhelming opinion from >> other developers that the code is fine, then we could ignore the >> dissenting developer. But unless there's *overwhelming* opinion >> that the patch is fine, I think that a single complaint of >> readability should render the patch un-pushable. > > +1. > Hmm, adopting this policy would make me the most feared reviewer in > the community :-P
Shrug. It is life insurance with the code as benefiter. Nobody wants to pay the premium, but if you don't, it won't survive for long after you lose life or just interest in it. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
