From: Joe Perches <joe@perches.com>
To: Nick Bowler <nbowler@elliptictech.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
anish singh <anish198519851985@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Andy Whitcroft <apw@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Validate signature styles and To: and Cc: lines
Date: Wed, 08 Jun 2011 13:40:47 -0700 [thread overview]
Message-ID: <1307565647.16453.18.camel@Joe-Laptop> (raw)
In-Reply-To: <20110608202408.GA20393@elliptictech.com>
On Wed, 2011-06-08 at 16:24 -0400, Nick Bowler wrote:
> On 2011-06-08 12:34 -0700, Joe Perches wrote:
> > Signatures have many forms and can sometimes cause problems
> > if not in the correct format when using git send-email or quilt.
> > Try to verify the signature tags and email addresses to use
> > the generally accepted "Signed-off-by: Full Name <email@domain.tld>"
> > form.
> [...]
> > + my $suggested_email = format_email(parse_email($email));
> > + if ($suggested_email eq "") {
> > + ERROR("email address '$email' is unrecognizable\n" . $herecurr);
> > + } elsif ($suggested_email ne $email) {
> > + WARN("email address '$email' might be better as '$suggested_email'\n" . $herecurr);
> If you're going to make suggestions, you should at the very least ensure
> that the suggestions are actually valid email addresses. Otherwise,
> this script will suggest replacing valid addresses with invalid ones!
Anyone that puts angle brackets in a quoted name
is pretty silly. There aren't any in git history.
What I did is pretty simple and covers most all
normally used cases.
You are free to improve email parsing.
next prev parent reply other threads:[~2011-06-08 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTi=AFbSXzjRHuY=uBFz=64C6vWLwNA@mail.gmail.com>
2011-06-08 19:34 ` Joe Perches
2011-06-08 20:24 ` Nick Bowler
2011-06-08 20:40 ` Joe Perches [this message]
2011-06-09 5:45 ` [PATCH V2] " 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=1307565647.16453.18.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=anish198519851985@gmail.com \
--cc=apw@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@elliptictech.com \
--cc=rdunlap@xenotime.net \
--cc=rostedt@goodmis.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
Powered by JetHome