Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265021AbTF1CU6 (ORCPT ); Fri, 27 Jun 2003 22:20:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265024AbTF1CU6 (ORCPT ); Fri, 27 Jun 2003 22:20:58 -0400 Received: from pao-ex01.pao.digeo.com ([12.47.58.20]:28763 "EHLO pao-ex01.pao.digeo.com") by vger.kernel.org with ESMTP id S265021AbTF1CUz (ORCPT ); Fri, 27 Jun 2003 22:20:55 -0400 Date: Fri, 27 Jun 2003 19:35:21 -0700 From: Andrew Morton To: "Martin J. Bligh" Cc: bcollins@debian.org, davidel@xmailserver.org, davem@redhat.com, linux-kernel@vger.kernel.org, linux-net@vger.kernel.org, netdev@oss.sgi.com Subject: Re: networking bugs and bugme.osdl.org Message-Id: <20030627193521.25040f3e.akpm@digeo.com> In-Reply-To: <36630000.1056766403@[10.10.2.4]> References: <20030626.224739.88478624.davem@redhat.com> <21740000.1056724453@[10.10.2.4]> <20030627.143738.41641928.davem@redhat.com> <20030627213153.GR501@phunnypharm.org> <20030627162527.714091ce.akpm@digeo.com> <35240000.1056760723@[10.10.2.4]> <20030627181432.61bf6f3a.akpm@digeo.com> <36630000.1056766403@[10.10.2.4]> X-Mailer: Sylpheed version 0.9.0pre1 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Jun 2003 02:35:10.0646 (UTC) FILETIME=[E5469560:01C33D1D] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2063 Lines: 53 "Martin J. Bligh" wrote: > > 1. default owners -> lists: > > Setting default owners to existing lists is somewhat invasive, and > might provoke riots ;-) Not only do you get the new bug notification, > but also any updates, which may become irritating. That's OK. It is a matter of people being aware that the updates will be echoed to a mailing list and acting appropriately. If some low-value stuff leaks through then ho-hum, at least it was on-topic. It is not as if we are unused to low-value content... It would be good if pure administrata such as changing the status were filtered. In fact, there is probably no point in sending anything bugzilla->list apart from the initial report. If the bug is then pursued via bugzilla then OK. If is is pursued via email then bugzilla just captures the discussion. > There's probably > some vaguely happy medium to be found between: > a) sending newly logged bugs to existing lists, > b) sending updates to some new list. > Maybe if we just create a new list for each category, and let > people subscribe at will to those ... and I keep sending newly logged > bugs to linux-kernel? I can cc netdev / linux-scsi / whatever on those > new ones if that helps? I think sending the initial report to the relevant lists and then capturing incoming email would suffice. > 2. email back in. > > Email back in is harder, and needs more thought as to how to make it > easy to use, whilst avoiding logging crap (eg. ensuing flamewars that > derive from the bug reports, etc). Well hopefully people will have the sense to cut the bugzilla address off the Cc line if it drifts off-topic. > My intuition is to log replies by > default, and hack off certain threads by hand Nah. Just log everything and hack off the crap by larting people. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/