Perhaps the subject line should be
Issue nnn:
where is the subject description, in view of that "in
project lilypond" is redundant on the Bug-Lilypond list (or use
"Lilypond issue nnn: ", and that one then doesn't have to
read the mail to see what it is about.
Also,
[EMAIL PROTECTED]
On 5 Jan 2007, at 14:28, Mats Bengtsson wrote:
An advantage of keeping it on the bug mailing list is that
- The person who originally reported the error will see the progress
without having to subscribe to yet another mailing list (at least
if (s)he
already subscribed to bug-lilypond to be
I'm missing something -- what "such stuff" is Hans referring? The
automatic updates of bugs?
I personally like it, since it saves me from having to subscribe to
every single bug in the tracker. For other people, it can be useful to
see what's happening -- ok, all the one-line "fixed / verifi
An advantage of keeping it on the bug mailing list is that
- The person who originally reported the error will see the progress
without having to subscribe to yet another mailing list (at least if (s)he
already subscribed to bug-lilypond to be able to send the bug report.
- The follow-up discuss
Hans Aberg escreveu:
> Bison has special mailing list for such stuff, Bison-Patches. - Perhaps
> something for LilyPond, too.
we have lilypond-cvs@gnu.org
Graham?
(I don't care either way.)
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- C
Bison has special mailing list for such stuff, Bison-Patches. -
Perhaps something for LilyPond, too.
Hans Aberg
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
