From: Brian Norris <computersforpeace@gmail.com>
To: <linux-kernel@vger.kernel.org>
Cc: Brian Norris <computersforpeace@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Joe Perches <joe@perches.com>
Subject: [PATCH v3 4/4] get_maintainer: --r (list reviewer) is on by default
Date: Wed, 4 Nov 2015 12:58:28 -0800 [thread overview]
Message-ID: <1446670708-122507-4-git-send-email-computersforpeace@gmail.com> (raw)
In-Reply-To: <1446670708-122507-1-git-send-email-computersforpeace@gmail.com>
We don't consistenly document the default value next to the option
listing, but we do have a list of defaults here, so let's keep it up to
date.
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Joe Perches <joe@perches.com>
---
v2 -> v3:
no change
v2:
new in v2
https://lkml.org/lkml/2015/11/4/480
scripts/get_maintainer.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
index 145f1bf6472e..0eec34ac45cd 100755
--- a/scripts/get_maintainer.pl
+++ b/scripts/get_maintainer.pl
@@ -813,7 +813,7 @@ Other options:
--help => show this help information
Default options:
- [--email --nogit --git-fallback --m --n --l --multiline --pattern-depth=0
+ [--email --nogit --git-fallback --m --r --n --l --multiline --pattern-depth=0
--remove-duplicates --rolestats]
Notes:
--
2.6.0.rc2.230.g3dd15c0
next prev parent reply other threads:[~2015-11-04 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 20:58 [PATCH v3 1/4] get_maintainer: add missing documentation for --git-blame-signatures Brian Norris
2015-11-04 20:58 ` [PATCH v3 2/4] get_maintainer: it's '--pattern-depth', not '-pattern-depth' Brian Norris
2015-11-04 20:58 ` [PATCH v3 3/4] get_maintainer: add --no-foo options to --help Brian Norris
2015-11-04 20:58 ` Brian Norris [this message]
2015-11-04 21:13 ` [PATCH v3 1/4] get_maintainer: add missing documentation for --git-blame-signatures 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=1446670708-122507-4-git-send-email-computersforpeace@gmail.com \
--to=computersforpeace@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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 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.