Warly wrote:
This is exactly what I thought about yesterday, but I was too busy to post this suggestion. Only post messages with a new comment (attachments are usually accompanied by a comment and so they do not need a separate posting) or with a state change to "Resolved" (perhaps also to "Reopened"?). Then the list gets much cleaner, without loss of important information.Nelson Bartley <[EMAIL PROTECTED]> writes:On Thu, 2002-12-19 at 19:39, Ben Reser wrote:On Thu, Dec 19, 2002 at 07:20:33PM +0100, Warly wrote:If most of you think bugzilla mail on cooker are useless, I can remove them and just shutdown bugzilla. The goal is not to annoy you, is to make our job cleare and easier in debugging period.<!snipped> I agree completely with Ben about the bugzilla setup. I understand you position warly on the use of bugzilla, I've had to use similar (though far simpler) troublshooting tools during beta periods for our OC48 Packet Over Sonet Cards we were designing at Nortel. The idea though was to ensure that, as Ben said, the people who need the information get it. If I'm troubleshooting a problem, which is largely unlikely as I'm no expert, I only need to be concerned with the problem. If I'm ready to solve a new one, I need to be able to see what's currently out there to solve, and pick it up.[...]The final note is this. You, Warly et Mandrakesoft, are in charge of this list. Though I appreciate that our concerns (eg the community ) are being listend to, in the end you make the policy, not us. If you choose to leave bugzilla as it is, then we will all just have to accept it or move on.Ok. I think I will try not to send any email that does not contains a comments. This is likely to remove all the status change only or think like that. But I may still send mail when the bug is marked as RESOLVED ?
Till
