From: "Uwe Kleine-König" <ukleinek@strlen.de>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] List of maintainers (draft #3)
Date: Mon, 22 Sep 2008 10:12:39 +0200 [thread overview]
Message-ID: <20080922081239.GA28726@strlen.de> (raw)
In-Reply-To: <200202071054.g17Asst06608@Port.imtp.ilyichevsk.odessa.ua>
On Thu, Feb 07, 2002 at 12:54:56PM -0200, Denis Vlasenko wrote:
> After recent discussion on Linux development practices I think it may be
> worthy to have list of lk maintainers. Unlike one included into kernel
> source, this document is meant to be monthly (weekly?) mailed to lkml
> and to be modified whenever new victim wishes to be listed in it
> or someone can no longer devote his time to maintainer work.
I don't see an advantage of a regular mail compared to a file in the
tree, but obviously YMMV.
But another thing really bothers me: I think there should not be more
than one place I have to look up manually for maintainers. Currently I
have ~100 easy patches pending and the most time consuming part of
finishing these is looking up the right address to send to send them to.
Currently I already have to check the modified files for a maintainer
entry, MAINTAINERS and the history of the files.
IMHO this could be automated with some effort. I currently imagine:
- a MAINTAINERS maintainer?!
- a certain format to specify a maintainer of a single file in that
file (e.g. in a specially marked comment) to prevent overloading
MAINTAINERS
- maybe a per-directory .maintainers file.
- add a field to each entry in MAINTAINERS specifying a regular
expression or shell wildcard of the corresponding files and
directories.
- a script that takes a patch and extracts the addresses from the above
sources (and optionally calls git send-email)
If you want to do that with an externally maintained source thats OK for
me, too, provided it eases patch submission.
Best regards
Uwe
next prev parent reply other threads:[~2008-09-22 8:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 14:54 [RFC] List of maintainers (draft #3) Denis Vlasenko
2008-09-22 8:12 ` Uwe Kleine-König [this message]
2008-09-22 9:12 ` Ben Dooks
2008-09-22 9:23 ` Pekka Enberg
2008-09-22 16:40 ` H. Peter Anvin
2008-09-22 19:42 ` Uwe Kleine-König
2008-09-23 5:10 ` Joe Perches
2008-09-29 17:56 ` Pavel Machek
2008-10-01 0:10 ` Randy Dunlap
2008-10-01 0:09 ` Joe Perches
2008-10-01 0:35 ` Randy Dunlap
2008-10-01 13:36 ` Pavel Machek
2008-10-01 15:41 ` Randy Dunlap
2008-10-01 12:25 ` [PATCH] [RFC] Add a script that searched per-file maintainers for a patch Uwe Kleine-König
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=20080922081239.GA28726@strlen.de \
--to=ukleinek@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.