On Monday 09 December 2002 16:50, Warly wrote: > I think there is 2 problems. > > - first one is technical, when you reply to the bug into cooker you > get your comment posted both by sympa an bugzilla, this I can fix. > > - second one is maintainers and subscribers problems. Some of them do > not care of bugzilla post, and filter them out. > > Creating a separate mailing list will ease the filtering problem of > the people of the second point, but guys who care about bugs will not > see any change except having to subscribe to two mailing lists instead > of one. > > As a consequence, I will try: > > - to fix the duplicate problem so that anyone could reply to a bug in > cooker without caring of the address is responding to. Bugzilla will > takes care not to send duplicates. > > - to make it clearer on bugzilla that it is only for development > version. And also to do an automatic search before the bug is posted > to ask user if by chance his bug is not already reported.
There is a bigger problem. The bugzilla post are unreadable. They start with https://qa.mandrakesoft.com/show_bug.cgi? which says nothing to me except when i go to that webpage. Than there is optional some extra info. After that you get the addition comment. aka the real meat of the reply and than you get the ------- You are receiving this mail because:-------. My suggestion is to start with addition comment because that is the important part of the message and than you can decide quickly if it is important for you or not. Than have the https stuff and than to remove the ------- You are receiving this mail because:------- part of the mail when it is send to the cooker list. I can see why one would add it to a email to a CC'er but on cooker it is just two more lines to (not)read.
