From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Randy Dunlap" <randy.dunlap@oracle.com>,
"Uwe Kleine-König" <ukleinek@strlen.de>,
"Pavel Machek" <pavel@suse.cz>
Subject: [PATCH 0/10] MAINTAINERS - add script and patterns
Date: Tue, 18 Nov 2008 09:13:12 -0800 [thread overview]
Message-ID: <1227028402-1548-1-git-send-email-joe@perches.com> (raw)
Now that "F:" is documented in MAINTAINERS, this patchset
adds a script to find the maintainer of an individual
file or files in a patch and additional patterns to
MAINTAINERS.
Other information from MAINTAINERS sections can
also be generated by file or patch.
Changes since last submission:
scripts/get_maintainers.pl is checkpatch clean
Changed patterns for recent renames
Added patterns for recent MAINTAINERS entries
Fix i2c-tiny-usb entry
Update FPU Emulator entry
1/10: Add scripts/get_maintainer.pl
2/10: MAINTAINERS - Add file patterns
3/10: MAINTAINERS - Standardize style
4/10: MAINTAINERS - Remove CS4280
5/10: MAINTAINERS - Remove HP Fibre Channel HBA no longer in tree
6/10: MAINTAINERS - Standardize "T: git urls"
7/10: MAINTAINERS - Add Linus Torvalds' git
8/10: MAINTAINERS - Add FTRACE git
9/10: MAINTAINERS - Fix i2c-tiny-usb entry
10/10: MAINTAINERS - Update FPU Emulator contact address and web page
$ ./scripts/get_maintainer.pl
usage: ./scripts/get_maintainer.pl [options] patchfile
./scripts/get_maintainer.pl [options] -f file
version: 0.12
MAINTAINER field selection options:
--email => print email address(es) if any
--git => include recent git *-by: signers
--git-chief-penguins => include (Linus Torvalds|Andrew Morton)
--m => include maintainer(s) if any
--n => include name 'Full Name <addr@domain.tld>'
--l => include list(s) if any
--s => include subscriber only list(s) if any
--scm => print SCM tree(s) if any
--status => print status if any
--subsystem => print subsystem name if any
--web => print website(s) if any
Output type options:
--separator [, ] => separator for multiple entries on 1 line
--multiline => print 1 entry per line
Default options:
[--email --git --m --l --multiline]
next reply other threads:[~2008-11-18 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 17:13 Joe Perches [this message]
2008-11-18 17:13 ` [PATCH 01/10] Add scripts/get_maintainer.pl Joe Perches
2008-11-18 17:13 ` [PATCH 02/10] MAINTAINERS - Add file patterns Joe Perches
2008-11-18 17:13 ` [PATCH 03/10] MAINTAINERS - Standardize style Joe Perches
2008-11-18 17:13 ` [PATCH 04/10] MAINTAINERS - Remove CS4280 Joe Perches
2008-11-18 17:13 ` [PATCH 05/10] MAINTAINERS - Remove HP Fibre Channel HBA no longer in tree Joe Perches
2008-11-18 17:13 ` [PATCH 06/10] MAINTAINERS - Standardize "T: git urls" Joe Perches
2008-11-18 17:13 ` [PATCH 07/10] MAINTAINERS - Add Linus Torvalds' git Joe Perches
2008-11-18 17:13 ` [PATCH 08/10] MAINTAINERS - Add FTRACE git Joe Perches
2008-11-18 17:13 ` [PATCH 09/10] MAINTAINERS - Fix i2c-tiny-usb entry Joe Perches
2008-11-18 17:13 ` [PATCH 10/10] MAINTAINERS - Update FPU Emulator contact address and web page 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=1227028402-1548-1-git-send-email-joe@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
--cc=ukleinek@strlen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®