From: Krzysztof Halasa <khc@pm.waw.pl>
To: Adrian Bunk <bunk@stusta.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Rene Herman <rene.herman@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Robert P. J. Day" <rpjday@mindspring.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marcel Holtmann <marcel@holtmann.org>,
Christoph Hellwig <hch@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: MODULE_MAINTAINER
Date: Thu, 26 Apr 2007 21:37:59 +0200 [thread overview]
Message-ID: <m38xcfhqp4.fsf@maximus.localdomain> (raw)
In-Reply-To: <20070426155205.GN3468@stusta.de> (Adrian Bunk's message of "Thu, 26 Apr 2007 17:52:06 +0200")
Adrian Bunk <bunk@stusta.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
next prev parent reply other threads:[~2007-04-26 19:38 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 11:26 MODULE_MAINTAINER Rene Herman
2007-04-04 11:29 ` MODULE_MAINTAINER Rene Herman
2007-04-04 12:33 ` MODULE_MAINTAINER Christoph Hellwig
2007-04-04 13:02 ` MODULE_MAINTAINER Rene Herman
2007-04-04 14:57 ` MODULE_MAINTAINER Adrian Bunk
2007-04-04 16:33 ` MODULE_MAINTAINER Stefan Richter
2007-04-04 16:38 ` MODULE_MAINTAINER Adrian Bunk
2007-04-04 16:45 ` MODULE_MAINTAINER Stefan Richter
2007-04-04 14:48 ` MODULE_MAINTAINER Marcel Holtmann
2007-04-04 15:02 ` MODULE_MAINTAINER Adrian Bunk
2007-04-04 15:50 ` MODULE_MAINTAINER Rene Herman
2007-04-04 16:00 ` MODULE_MAINTAINER Alan Cox
2007-04-04 16:06 ` MODULE_MAINTAINER Marcel Holtmann
2007-04-04 16:38 ` MODULE_MAINTAINER Rene Herman
2007-04-04 17:00 ` MODULE_MAINTAINER Takashi Iwai
2007-04-04 17:48 ` MODULE_MAINTAINER Adrian Bunk
2007-04-04 18:01 ` MODULE_MAINTAINER Rene Herman
2007-04-04 19:12 ` MODULE_MAINTAINER Adrian Bunk
2007-04-05 0:08 ` MODULE_MAINTAINER Stefan Richter
2007-04-23 9:33 ` MODULE_MAINTAINER Rene Herman
2007-04-23 11:24 ` MODULE_MAINTAINER Rusty Russell
2007-04-23 11:52 ` MODULE_MAINTAINER Robert P. J. Day
2007-04-23 12:00 ` MODULE_MAINTAINER Robert P. J. Day
2007-04-23 12:32 ` MODULE_MAINTAINER Rene Herman
2007-04-26 1:18 ` MODULE_MAINTAINER Andrew Morton
2007-04-26 10:03 ` MODULE_MAINTAINER Rusty Russell
2007-04-26 10:41 ` MODULE_MAINTAINER Rene Herman
2007-04-26 13:54 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 14:55 ` MODULE_MAINTAINER Rene Herman
2007-04-26 16:00 ` MODULE_MAINTAINER Alan Cox
2007-04-26 16:45 ` MODULE_MAINTAINER Rene Herman
2007-04-26 15:41 ` MODULE_MAINTAINER Randy Dunlap
2007-04-26 15:52 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 16:44 ` MODULE_MAINTAINER Randy Dunlap
2007-04-26 17:12 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 19:37 ` Krzysztof Halasa [this message]
2007-04-26 19:43 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 20:02 ` MODULE_MAINTAINER Krzysztof Halasa
2007-04-26 20:24 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 21:51 ` MODULE_MAINTAINER Krzysztof Halasa
2007-04-26 22:01 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 22:07 ` MODULE_MAINTAINER Krzysztof Halasa
2007-04-26 22:28 ` MODULE_MAINTAINER Rene Herman
2007-04-26 20:11 ` MODULE_MAINTAINER Rene Herman
2007-04-26 22:24 ` MODULE_MAINTAINER Gene Heskett
2007-04-27 9:06 ` MODULE_MAINTAINER Stefan Richter
2007-04-26 22:03 ` MODULE_MAINTAINER Rene Herman
2007-04-27 21:06 ` MODULE_MAINTAINER Rene Herman
2007-04-28 21:03 ` MODULE_MAINTAINER Krzysztof Halasa
2007-04-23 23:46 ` MODULE_MAINTAINER Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38xcfhqp4.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=randy.dunlap@oracle.com \
--cc=rene.herman@gmail.com \
--cc=rpjday@mindspring.com \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox