From: "Uwe Kleine-König" <ukleinek@strlen.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
randy.dunlap@oracle.com
Subject: Re: [PATCH 1/8] Add scripts/get_maintainer.pl
Date: Thu, 30 Oct 2008 23:43:31 +0100 [thread overview]
Message-ID: <20081030224331.GA30814@strlen.de> (raw)
In-Reply-To: <20081030104136.GB32389@atrey.karlin.mff.cuni.cz>
Hello,
> > Also, this:
> >
> > MAINTAINERS | 1096 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> > 1 file changed, 1094 insertions(+), 2 deletions(-)
> >
> > isn't practical for me or Stephen to carry, I'm afraid. That's
> > probably the most-patched file in the kernel. This will need to be a
> > direct you->Linus thing.
> >
> > I think the feature is sorely needed and will prove useful.
>
> Would you be willing to merge the scripts etc, leaving only
> MAINTAINERS file for direct merge with Linus, preferably at the -rc5
> or something?
I still think that the source files should (additionally) be parsed
somehow, too. Something like
/*
* TOPIC
* P: A. U. Thor <author@examp.l.e>
* M: lkml@kernel.org
*/
at the beginning of a file. The advantage is that MAINTAINERS doesn't
need to have an entry for each driver and so the F: field cannot become
inconsistent and the author doesn't need to bother getting the entry
into MAINTAINERS---just the driver file is enough.
Best regards
Uwe
next prev parent reply other threads:[~2008-10-30 22:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 23:09 [PATCH 0/8] MAINTAINERS - add script and patterns Joe Perches
2008-10-23 23:09 ` [PATCH 1/8] Add scripts/get_maintainer.pl Joe Perches
2008-10-23 23:09 ` [PATCH 2/8] MAINTAINERS - Add file patterns Joe Perches
2008-10-23 23:09 ` [PATCH 3/8] MAINTAINERS - Standardize style Joe Perches
2008-10-23 23:09 ` [PATCH 4/8] MAINTAINERS - remove CS4280 Joe Perches
2008-10-23 23:09 ` [PATCH 5/8] MAINTAINERS - Remove HP Fibre Channel HBA no longer in tree Joe Perches
2008-10-23 23:09 ` [PATCH 6/8] MAINTAINERS - standardize "T: git urls" Joe Perches
2008-10-23 23:09 ` [PATCH 7/8] MAINTAINERS - Add Linus Torvalds' git Joe Perches
2008-10-23 23:09 ` [PATCH 8/8] MAINTAINERS - Add FTRACE git Joe Perches
2008-10-27 22:52 ` [PATCH 1/8] Add scripts/get_maintainer.pl Andrew Morton
2008-10-27 23:46 ` Joe Perches
2008-10-28 0:44 ` Joe Perches
2008-10-30 10:41 ` Pavel Machek
2008-10-30 22:43 ` Uwe Kleine-König [this message]
2008-10-25 7:41 ` [PATCH 0/8] MAINTAINERS - add script and patterns Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2009-03-17 23:19 Joe Perches
2009-03-17 23:19 ` [PATCH 1/8] Add scripts/get_maintainer.pl Joe Perches
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=20081030224331.GA30814@strlen.de \
--to=ukleinek@strlen.de \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=randy.dunlap@oracle.com \
--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