Comment #21 on issue 1815 by percival.music.ca: lilypond-book fails on Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
Patchy just makes sure there's no blindingly huge problems. A complete inability to run lilypond on windows (or osx) is a huge problem, but not a "blindingly huge" one. :)
There's still the review phase (for any humans willing to look at it), and the unstable release phase (for any users silly enough to run an unstable development version). The whole point of Patchy is to filter out obviously wrong patches before a human spends time looking at it.
NB: if any developer wants to ask for help/reviews for a patch, knowing that it won't apply to master, doesn't compile, or introduces regressions, go for it! Just use the --no-code-issue and/or use the patch-needs_work label. Patchy is only supposed to check patches that would otherwise be added to master, not "discussion" patches.
_______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
