From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] How to (automatically) find the correct maintainer(s)
Date: Sun, 14 Jan 2007 00:41:37 +0100 [thread overview]
Message-ID: <45A96E31.3080307@student.ltu.se> (raw)
In-Reply-To: <45A93B02.7040301@citd.de>
Matthias Schniedermeyer wrote:
> Richard Knutsson wrote:
>
>
>> Any thoughts on this is very much appreciated (is there any flaws with
>> this?).
>>
>
> The thought that crossed my mind was:
>
> Why not do the same thing that was done to the "Help"-file. (Before it
> was superseded by Kconfig).
>
> Originaly there was a central Help-file, with all the texts. Then it was
> split and placed in each sub-dir. And later it was superseded by Kconfig.
>
> On the other hand you could skip the intermediate step and just fold the
> Maintainer-data directly into Kconfig, that way everything is "in one
> place" and you could place a "Maintainers"-Button next to the
> "Help"-Button in *config, or just display it alongside the help.
>
> And MAYBE that would also lessen the "update-to-date"-problem, as you
> can just write the MAINTAINERs-data when you create/update the
> Kconfig-file. Which is a thing that creates much bigger pain when you
> forget it accidently. ;-)
>
> Oh, and it neadly solves the mapping-problem, for at least all
> kernel-parts that have a Kconfig-option/Sub-Tree.
>
I'm all for splitting up the MAINTAINERS! :)
Just, do you have any ideas how to solve the possible multiple of the
same entries, when handling multiple sub-directories and when many
different drivers with different maintainers are in the same directory
and a maintainer have more then one driver?
next prev parent reply other threads:[~2007-01-13 23:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 16:30 [RFC] How to (automatically) find the correct maintainer(s) Richard Knutsson
2007-01-13 17:16 ` Stefan Richter
2007-01-13 19:18 ` Richard Knutsson
2007-01-13 20:15 ` Stefan Richter
2007-01-13 23:33 ` Richard Knutsson
2007-01-14 1:00 ` Stefan Richter
2007-01-14 1:02 ` Stefan Richter
2007-01-14 21:28 ` Richard Knutsson
2007-01-14 22:44 ` Stefan Richter
2007-01-15 18:39 ` Richard Knutsson
2007-01-15 20:06 ` Stefan Richter
2007-01-13 20:03 ` Matthias Schniedermeyer
2007-01-13 23:41 ` Richard Knutsson [this message]
2007-01-14 0:04 ` Matthias Schniedermeyer
2007-01-14 21:42 ` Richard Knutsson
2007-01-14 23:04 ` Stefan Richter
2007-01-15 0:01 ` Matthias Schniedermeyer
2007-01-15 0:43 ` Stefan Richter
2007-01-15 18:01 ` Richard Knutsson
2007-01-15 20:05 ` Matthias Schniedermeyer
2007-01-15 20:21 ` Richard Knutsson
2007-01-14 23:36 ` Matthias Schniedermeyer
2007-01-22 19:56 ` Andrew Morton
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=45A96E31.3080307@student.ltu.se \
--to=ricknu-0@student.ltu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@citd.de \
/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.