From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Satyam Sharma <satyam@infradead.org>,
Arjan van de Ven <arjan@infradead.org>,
Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
Joe Perches <joe@perches.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
Date: Mon, 13 Aug 2007 21:53:15 +0200 [thread overview]
Message-ID: <46C0B6AB.5010908@student.ltu.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0708132120520.30582@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Aug 14 2007 00:02, Satyam Sharma wrote:
>
>> Better solution is to have multiple MAINTAINERS files distributed in the
>> kernel tree, IMHO -- say a drivers/net/MAINTAINERS for maintainer info on
>> all various net drivers, drivers/kvm/MAINTAINERS for KVM maintainer info,
>> fs/ext3/MAINTAINERS for ext3 maintainers, fs/MAINTAINERS for generic VFS
>> maintainers info, so on and so forth. Of course, these individual
>> MAINTAINERS files could still have the newly-introduced "F:" fields as
>> well (drivers/net/MAINTAINERS would clearly require it, f.e.) ...
>>
>
> Yes please.
>
> Or perhaps even putting the maintainer into the Kconfig files?
>
>
Hope I am not biting my ass now, but I believed this was suggested but
the counter-argument were; is really a file/system made to configure the
kernel related to the maintainer?
I like the idea of ".maintainers" (or maybe even ".maintainer" now). It
has also been suggested that the file should be at the lowest common
pathway to avoid duplication. Downside is the added need to search for
the file...
Richard Knutsson
next prev parent reply other threads:[~2007-08-13 19:55 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 5:49 [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl Joe Perches
2007-08-13 6:42 ` Michal Piotrowski
2007-08-13 7:16 ` Al Viro
2007-08-13 16:22 ` Sam Ravnborg
2007-08-13 17:40 ` Rene Herman
2007-08-13 15:43 ` Kok, Auke
2007-08-13 19:40 ` Richard Knutsson
2007-08-13 20:28 ` Kok, Auke
2007-08-13 20:43 ` Richard Knutsson
2007-08-13 17:09 ` Ray Lee
2007-08-13 18:11 ` Valdis.Kletnieks
2007-08-13 21:04 ` Adrian Bunk
2007-08-13 17:33 ` Mariusz Kozlowski
2007-08-13 17:42 ` Arjan van de Ven
2007-08-13 18:07 ` Mariusz Kozlowski
2007-08-13 18:10 ` Rene Herman
2007-08-13 18:32 ` Satyam Sharma
2007-08-13 19:21 ` Jan Engelhardt
2007-08-13 19:53 ` Richard Knutsson [this message]
2007-08-13 20:05 ` Valdis.Kletnieks
2007-08-13 18:41 ` Krzysztof Halasa
2007-08-13 19:02 ` Krzysztof Halasa
2007-08-13 20:16 ` Theodore Tso
2007-08-13 20:37 ` Trond Myklebust
2007-08-14 1:19 ` Arjan van de Ven
2007-08-14 1:48 ` John W. Linville
2007-08-14 1:51 ` Rene Herman
2007-08-14 2:04 ` Rene Herman
2007-08-14 9:20 ` Alan Cox
2007-08-14 13:47 ` Arjan van de Ven
2007-08-14 14:28 ` Adrian Bunk
2007-08-14 14:33 ` Arjan van de Ven
2007-08-14 15:53 ` Rene Herman
2007-08-14 17:00 ` Joe Perches
2007-08-14 18:03 ` Rene Herman
2007-08-14 18:28 ` Joe Perches
2007-08-14 18:33 ` Rene Herman
2007-08-14 18:40 ` Linus Torvalds
2007-08-14 18:54 ` Joe Perches
2007-08-14 19:33 ` Al Viro
2007-08-14 19:57 ` Joe Perches
2007-08-15 1:19 ` Rene Herman
2007-08-15 13:33 ` Satyam Sharma
2007-08-15 13:39 ` Rene Herman
2007-08-15 13:52 ` Kyle Moffett
2007-08-16 10:58 ` Rene Herman
2007-08-16 11:08 ` Rene Herman
2007-08-16 11:26 ` Salikh Zakirov
2007-08-16 11:57 ` Rene Herman
2007-08-16 15:40 ` Al Viro
2007-08-16 15:53 ` Rene Herman
2007-08-16 19:00 ` Junio C Hamano
2007-08-17 4:24 ` Rene Herman
2007-08-15 19:37 ` Krzysztof Halasa
2007-08-15 23:19 ` Al Viro
2007-08-15 1:35 ` Richard Knutsson
2007-08-15 9:29 ` Stefan Richter
2007-08-15 15:31 ` Ray Lee
2007-08-16 20:36 ` Joe Perches
2007-08-15 1:31 ` Junio C Hamano
2007-08-15 2:12 ` Joe Perches
2007-08-15 5:25 ` Junio C Hamano
2007-08-15 5:42 ` Rene Herman
2007-08-15 9:39 ` Stefan Richter
2007-08-15 11:44 ` Rene Herman
2007-08-15 17:26 ` Joe Perches
2007-08-17 2:13 ` Joe Perches
2007-08-17 2:30 ` Joe Perches
2007-08-17 17:54 ` [PATCH] - git-send-email.perl Joe Perches
2007-08-17 23:38 ` Junio C Hamano
2007-08-18 1:51 ` Joe Perches
2007-08-14 14:22 ` [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl Adrian Bunk
2007-08-14 14:33 ` Arjan van de Ven
2007-08-14 14:45 ` John W. Linville
2007-08-14 2:15 ` Manu Abraham
-- strict thread matches above, loose matches on Subject: below --
2007-08-13 6:09 Joe Perches
2007-08-13 16:24 ` Sam Ravnborg
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=46C0B6AB.5010908@student.ltu.se \
--to=ricknu-0@student.ltu.se \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=jengelh@computergmbh.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
--cc=satyam@infradead.org \
--cc=torvalds@linux-foundation.org \
/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