On Mon, Sep 6, 2010 at 3:59 PM, Phil Holmes <[email protected]> wrote: > <[email protected]> wrote in message > news:5-9567054385019064696-277111724243982225-lilypond=googlecode....@googlecode.com... >> Comment #5 on issue 1124 by percival.music.ca: implement \eyeglasses using >> a 'path expression >> http://code.google.com/p/lilypond/issues/detail?id=1124 >> >> To verify this issue, I clicked on the link that Patrick provided, to >> check that the patch actually was pushed. >> >> I don't understand why it took 22 days to check that link. > > FWIW I don't think it can be verified in Windows, since I don't seem able to > write SVG files.
Oh good heavens, I didn't produce a svg file! I just check to see if the web git interface reported that the patch was added to lilypond. It might be nice to do more diligence in verifying issues, but we clearly don't have the resources for that. As long as you know what you're doing, 90% of issues should be verifiable within 60 seconds. Ok, maybe that's a slight exaggeration... but certainly 80% within 120 seconds. If you think there's a bunch of issues that require more effort than that, let's talk and decide on which corners to cut. I'm very serious about this -- it's important that the Bug Squad stays "current". I am absolutely willing to sacrifice quality / ease-of-reporting in order to keep things moving along. (that's why we insist on users producing Tiny bug reports, after all!) If anybody doesn't like this sacrifice of quality, then step forward and offer to do Bug Squad work. Cheers, - Graham _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
