Re: Issue nnn in project lilypond

[Hans Aberg]

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 able to send the bug report.
> - The follow-up discussions will go to the relevant mailing list  
> (bug-lilypond)
>  and Han-Wen/Graham can respond to the discussion by entering  
> something
>  in the bug tracker - there's no need to duplicate the answers both  
> here and
>  in the bug tracker.

With Bison, the actual implementations, especially the patches then  
(the code itself), go to Bison-Patches. No-code discussions  
generally, as well as feature suggestions, go to Bug-Bison. Help goes  
to Help-Bison.

LilyPond has different needs. I felt I wanted to see the LilyPond  
bugs reporting, but this stuff became too much traffic. Perhaps it  
falls between Patches and Bugs, and should have mailing list of its own.

> It's easy to add a filter in your email client if you're not  
> interested in the
> Issue nnn emails.

This is only a makeshift solution.

Otherwise: whatever is fine with me. I just wanted to bring the issue  
up.

  Hans Aberg