From: Ben Hutchings <ben@decadent.org.uk>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] scripts/get_maintainer.pl: Add --roles and --rolestats
Date: Sun, 18 Oct 2009 00:23:01 +0100 [thread overview]
Message-ID: <1255821781.2488.643.camel@localhost> (raw)
In-Reply-To: <6a3d8d2c4775189d3f854bdd25a87b0d2e37987e.1255811956.git.joe@perches.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
On Sat, 2009-10-17 at 13:47 -0700, Joe Perches wrote:
> --roles shows the role of each email address, i.e. why it was selected.
> --rolestats selects --roles and adds git log/blame signers #'s and %
>
> Multiple roles are possible (supporter, maintainer, git-signer...)
>
> --roles or --rolestats is meant to help identify appropriate maintainers
> to notify and should not be used with "git send-email --cc-cmd"
[...]
> Other changes:
>
> Format git-signers email addresses a bit to reduce bad signatures
> Command line bad arguments emitted a verbose usage(), just show --help
> Version number bumped to .22
>
> Ben Hutchings <ben@decadent.org.uk> had the idea and created a good deal
> of this implementation.
You're too modest!
> Signed-off-by: Joe Perches <joe@perches.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Ben.
--
Ben Hutchings
It is impossible to make anything foolproof because fools are so ingenious.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2009-10-17 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 20:47 [PATCH 1/1] scripts/get_maintainer.pl: Add --roles and --rolestats Joe Perches
2009-10-17 21:07 ` Greg KH
2009-10-17 23:23 ` Ben Hutchings [this message]
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=1255821781.2488.643.camel@localhost \
--to=ben@decadent.org.uk \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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