Comment #3 on issue 1530 by percival.music.ca: [PATCH] Fret diagram fixes (Issue 4176056)
http://code.google.com/p/lilypond/issues/detail?id=1530
James - for normal issues, yes, that would be appropriate. But for patch-issues, these links are all we need. Real discussion happens on -devel or codereview, and I don't want to complicate the "here is a patch; we needs to look at it" essential workflow.
At some point in the future, we may well move these "patch issues" somewhere else. (I'm flabbergasted that codereview offers no way to track patches per-project; that would make this entire thing ridiculously simple! and it's a ridiculously easy feature for them to add! grr!)
but for now, a single link to a -devel email (or two links: -devel email, and codereview if it exists) is all we need.
_______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
