From: Brian Norris <computersforpeace@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Brian Norris <computersforpeace@gmail.com>, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] get_maintainer: add missing documentation for --[no]git-blame-signatures
Date: Wed, 19 Aug 2015 15:09:40 -0700 [thread overview]
Message-ID: <1440022180-71428-2-git-send-email-computersforpeace@gmail.com> (raw)
In-Reply-To: <1440022180-71428-1-git-send-email-computersforpeace@gmail.com>
I really haven't used this option much myself, so feel free to improve
on the documentation for it.
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
---
scripts/get_maintainer.pl | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
index 04ae47a8a5bd..a57b4d462360 100755
--- a/scripts/get_maintainer.pl
+++ b/scripts/get_maintainer.pl
@@ -781,6 +781,7 @@ MAINTAINER field selection options:
--git-max-maintainers => maximum maintainers to add (default: $email_git_max_maintainers)
--git-min-percent => minimum percentage of commits required (default: $email_git_min_percent)
--[no]git-blame => use git blame to find modified commits for patch or file
+ --[no]git-blame-signatures => like --git-blame, but include all commit signers
--git-since => git history to use (default: $email_git_since)
--hg-since => hg history to use (default: $email_hg_since)
--[no]interactive => display a menu (mostly useful if used with the --git option)
--
2.5.0.276.gf5e568e
next prev parent reply other threads:[~2015-08-19 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 22:09 [PATCH 1/2] get_maintainer: add --no-foo options to --help Brian Norris
2015-08-19 22:09 ` Brian Norris [this message]
2015-10-14 17:10 ` Brian Norris
2015-10-14 17:15 ` Joe Perches
2015-10-14 17:33 ` Brian Norris
2015-10-14 17:38 ` 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=1440022180-71428-2-git-send-email-computersforpeace@gmail.com \
--to=computersforpeace@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox