From: Nick Bowler <nbowler@elliptictech.com>
To: Joe Perches <joe@perches.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, 8 Jun 2011 16:24:08 -0400 [thread overview]
Message-ID: <20110608202408.GA20393@elliptictech.com> (raw)
In-Reply-To: <100617f66cdceab04a87514d47929a4ec3aebc19.1307561278.git.joe@perches.com>
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!
In particular, angle brackets inside "quotes" or (comments) will
seriously trip up this script. For example:
WARNING: email address '"Foo Bar <x124>" <fbar@example.org>' might be
better as 'Foo Bar <x124>"<fbar@example.org>' #8:
Signed-off-by: "Foo Bar <x124>" <fbar@example.org>
Even more amusing is that we can actually follow the bogus suggestion
and checkpatch.pl won't complain about the resulting invalid email
address (at least it's consistent, I guess):
Signed-off-by: Foo Bar <x124>"<fbar@example.org>
patch has no obvious style problems and is ready for submission.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2011-06-08 20:24 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 ` [PATCH] checkpatch: Validate signature styles and To: and Cc: lines Joe Perches
2011-06-08 20:24 ` Nick Bowler [this message]
2011-06-08 20:40 ` Joe Perches
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=20110608202408.GA20393@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=akpm@linux-foundation.org \
--cc=anish198519851985@gmail.com \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--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