From: Adrian Bunk <bunk@stusta.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>,
Rene Herman <rene.herman@gmail.com>,
Rusty Russell <rusty@rustcorp.com.au>,
randy.dunlap@oracle.com, akpm@linux-foundation.org,
rpjday@mindspring.com, marcel@holtmann.org, hch@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] module_author: don't advice putting in an email address
Date: Sat, 12 May 2007 09:14:55 +0200 [thread overview]
Message-ID: <20070512071455.GH7984@stusta.de> (raw)
In-Reply-To: <20070511223500.01fe6596@the-village.bc.nu>
On Fri, May 11, 2007 at 10:35:00PM +0100, Alan Cox wrote:
> > This still wouldn't solve the following problems:
> > - I doubt it will be kept up to date for all > 2800 modules in the kernel
> > - the 3 year old kernel of your distribution would contain 3 year old
> > maintainership information
> > - maintainers sometimes disappear
>
> Maintainers sometimes DON'T disappear ....
No disagreement about that.
But things like disappearing maintainers, unmaintained code, and
maintainership that is at most informal (e.g. currently the floppy
driver) are real-life problems that do occur in several cases.
> > The default for "bug and defect reports" should be for all modules (as
> > well as for non-modular code) from ftp.kernel.org kernels either
> > linux-kernel or the kernel Bugzilla. [1]
>
> If users put it in the kernel bugzilla its gets lost because most of the
> bugzilla isn't set up to route bugs to maintainers. In the unlikely event
Bugzilla is actually setup to route bugs of the maintainer, this is
currently implemented through the Bugzilla feature "Andrew"...
> it arrives there or it gets posted to linux-kernel the only reply is
> "report it to your distributor"
>
> > For distribution kernels (which are what most users are using), the
> > default for "bug and defect reports" should be the distribution support.
>
> I'd prefer not. I get reports from people about drivers that got "lost"
> by vendors, regularly. Nor am I pointing fingers at specific vendors here,
> last month I sorted out a two year old "lost in Red Hat Bugzilla" kernel
> bug for example.
How many maintainers want to get bug reports against the kernel 2.6.9
shipped with RHEL 4?
> Alan
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-05-12 7:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 0:50 [PATCH] module_author: don't advice putting in an email address Rene Herman
2007-05-11 10:46 ` Alan Cox
2007-05-11 11:42 ` John Anthony Kazos Jr.
2007-05-11 20:50 ` Rene Herman
2007-05-11 21:18 ` Adrian Bunk
2007-05-11 21:35 ` Alan Cox
2007-05-12 7:14 ` Adrian Bunk [this message]
2007-05-12 12:15 ` Alan Cox
2007-05-12 12:38 ` Adrian Bunk
2007-05-11 14:16 ` Rene Herman
2007-05-11 14:40 ` Alan Cox
2007-05-11 17:21 ` Rene Herman
2007-05-11 23:23 ` Krzysztof Halasa
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=20070512071455.GH7984@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=jakj@j-a-k-j.com \
--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