From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David S. Miller" Subject: Re: networking bugs and bugme.osdl.org Date: Fri, 27 Jun 2003 17:44:40 -0700 (PDT) Sender: netdev-bounce@oss.sgi.com Message-ID: <20030627.174440.59660428.davem@redhat.com> References: <20030627.144426.71096593.davem@redhat.com> <1230000.1056754041@[10.10.2.4]> <20030627225305.GA13785@work.bitmover.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: mbligh@aracnet.com, greearb@candelatech.com, linux-kernel@vger.kernel.org, linux-net@vger.kernel.org, netdev@oss.sgi.com Return-path: To: lm@bitmover.com In-Reply-To: <20030627225305.GA13785@work.bitmover.com> Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org From: Larry McVoy Date: Fri, 27 Jun 2003 15:53:05 -0700 - one key observation: let bugs "expire" much like news expires. If nobody has been whining enough that it gets into the high signal bug db then it probably isn't real. We really want a way where no activity means let it expire. I want more than time based expiry, I want expiry for me that is controlled by me. When I delete the notification email in my mailbox, I never want to see that bug again unless I want to. This effectively degrades into list posting based bug reports and my current email inbox, which is what I'm advocating to use :-) When I see the "me too, heres some more info" response to the list posting, then I'm interested and I'll reread the list thread to digest all the information to see what I can make of it. When this happens bugs basically fix themselves, and this occurs only because of the acts taken on by the reporters of the bug not me.