Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 19 Dec 2002 15:25:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 19 Dec 2002 15:25:23 -0500 Received: from [81.2.122.30] ([81.2.122.30]:2825 "EHLO darkstar.example.net") by vger.kernel.org with ESMTP id ; Thu, 19 Dec 2002 15:25:21 -0500 From: John Bradford Message-Id: <200212192045.gBJKj4kk002703@darkstar.example.net> Subject: Re: Dedicated kernel bug database To: eli.carter@inet.com (Eli Carter) Date: Thu, 19 Dec 2002 20:45:04 +0000 (GMT) Cc: linux-kernel@vger.kernel.org In-Reply-To: <3E022B01.2030205@inet.com> from "Eli Carter" at Dec 19, 2002 02:24:33 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 959 Lines: 22 > > In any case, people could take the kernel bug database, and > > genericify it, much more easily than somebody could tailor an existing > > bug tracking application to the needs of the kernel, (which is > > demonstrated by the fact that the developers are not getting Bugzilla > > reports). > > Perhaps, but I'm not convinced that it would be easier to write a kernel > bug database from scratch than it would be to improve an existing > project to address the kernel's needs. And _that_ is what we were > discussing. Ah, well no wonder we're not agreeing :-), I actually saw the re-writing from scratch as being easier :-). Maybe I am just in the minority in that I don't find Bugzilla intuitive. John. - 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/