[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m38xcfhqp4.fsf@maximus.localdomain>
Date: Thu, 26 Apr 2007 21:37:59 +0200
From: Krzysztof Halasa <khc@...waw.pl>
To: Adrian Bunk <bunk@...sta.de>
Cc: Randy Dunlap <randy.dunlap@...cle.com>,
Rene Herman <rene.herman@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Robert P. J. Day" <rpjday@...dspring.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Marcel Holtmann <marcel@...tmann.org>,
Christoph Hellwig <hch@...radead.org>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: MODULE_MAINTAINER
Adrian Bunk <bunk@...sta.de> writes:
> I don't think we want to expose maintainership information to users at
> all:
> - duplicates information in MAINTAINERS
> - maintainers sometimes disappear
> - the 3 year old kernel of your distribution would contain 3 year old
> maintainership information
Right. Summary: adding maintainer info to source code and/or
compiled modules doesn't seem to make any sense.
> IMHO the default should be that users report problems with distribution
> kernels to their distribution and problems with ftp.kernel.org kernels
> to either linux-kernel or the kernel Bugzilla.
Yep. But it's really easy to miss something in lkml and/or in
more specific lists, and the Bugzilla isn't email. That means
we need a WWW-browseable database, with:
a) maintainers registrations with a simple email verification or
something like that
b) possibility for registered people to declare they now maintain
(or not) specific portions of the kernel
c) possibility for anyone to retrieve this information.
Other options?
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists