From: "H. Peter Anvin" <hpa@zytor.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: MAINTAINERS: standardize James Bottomley's name
Date: Mon, 03 Aug 2009 14:03:22 -0700 [thread overview]
Message-ID: <4A77509A.3010401@zytor.com> (raw)
In-Reply-To: <1249332233.3943.211.camel@mulgrave.site>
On 08/03/2009 01:43 PM, James Bottomley wrote:
> On Mon, 2009-08-03 at 13:32 -0700, Joe Perches wrote:
>> His recent patches and sign-offs have not used "E.J."
>>
>> This reduces the likelihood that get_maintainers.pl will
>> list his address twice.
>
> It is standard: I like my initials; which, per RFC requires the quotes
> because it's a mailing address.
>
It's not actually required by RFC 2822.
The relevant productions are:
name-addr = [display-name] angle-addr
display-name = phrase
phrase = 1*word / obs-phrase
obs-phrase = word *(word / "." / CFWS)
Now, obs- usually indicates an obsolete (deprecated
backwards-compatibility) production, but the text states:
Note: The "period" (or "full stop") character (".") in obs-phrase is
not a form that was allowed in earlier versions of this or any other
standard. Period (nor any other character from specials) was not
allowed in phrase because it introduced a parsing difficulty
distinguishing between phrases and portions of an addr-spec (see
section 4.4). It appears here because the period character is
currently used in many messages in the display-name portion of
addresses, especially for initials in names, and therefore must be
interpreted properly. In the future, period may appear in the
regular syntax of phrase.
-hpa
next prev parent reply other threads:[~2009-08-03 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 20:32 MAINTAINERS: standardize James Bottomley's name Joe Perches
2009-08-03 20:43 ` James Bottomley
2009-08-03 21:03 ` H. Peter Anvin [this message]
2009-08-03 21:22 ` Frans Pop
2009-08-03 22:03 ` H. Peter Anvin
2009-08-03 21:11 ` Joe Perches
2009-08-03 21:29 ` James Bottomley
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=4A77509A.3010401@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@HansenPartnership.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.