MAINTAINERS: standardize James Bottomley's name
His recent patches and sign-offs have not used "E.J."
This reduces the likelihood that get_maintainers.pl will list his address twice.
Section "MISCELLANEOUS MCA-SUPPORT" already uses this style.
MAINTAINERS +4 -4
@@ -137,7 +137,7 @@ S: Supported F: drivers/scsi/3w-xxxx* 53C700 AND 53C700-66 SCSI DRIVER -M: "James E.J. Bottomley" <[email protected]> +M: James Bottomley <[email protected]> L: [email protected] S: Maintained F: drivers/scsi/53c700*
@@ -3033,7 +3033,7 @@ F: include/*/lapb.h F: net/lapb/ LASI 53c700 driver for PARISC -M: "James E.J. Bottomley" <[email protected]> +M: James Bottomley <[email protected]> L: [email protected] S: Maintained F: Documentation/scsi/53c700.txt
@@ -3469,7 +3469,7 @@ S: Maintained F: fs/ncpfs/ NCR DUAL 700 SCSI DRIVER (MICROCHANNEL) -M: "James E.J. Bottomley" <[email protected]> +M: James Bottomley <[email protected]> L: [email protected] S: Maintained F: drivers/scsi/NCR_D700.*
@@ -4394,7 +4394,7 @@ F: drivers/scsi/sg.c F: include/scsi/sg.h SCSI SUBSYSTEM -M: "James E.J. Bottomley" <[email protected]> +M: James Bottomley <[email protected]> L: [email protected] T: git git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git T: git git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git
Quoted 4 lines · Joe Perches
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.
James
Quoted 9 lines · James Bottomley
Quoted 4 lines · Joe Perches
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
Quoted 13 lines · H. Peter Anvin
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.
Interesting.
Does that mean that vger can stop refusing mails because they include an address that has an unquoted name with initials?
Quoted 15 lines · Frans Pop
Quoted 13 lines · H. Peter Anvin
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.
Quoted 4 lines
Interesting.
Does that mean that vger can stop refusing mails because they include an address that has an unquoted name with initials?
If it does it's not RFC 2822 compliant.
-hpa
Quoted 8 lines · James Bottomley
Quoted 4 lines · Joe Perches
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.
Then change the other entry.
And if you really like your initials, you should probably change the email address format you're using right now and probably the mechanism you use to send your patches and acks as well.
Look at the name I'm replying to: (no quotes)
"James Bottomley <[email protected]>"
Right now, if somebody uses get_maintainers.pl on a patch for a file in drivers/scsi, git will find your signoffs as
(no quotes)
"James Bottomley <[email protected]>"
and the scripts/get_maintainers.pl will use MAINTAINERS entry of
(with quotes)
"James E.J. Bottomley <[email protected]>"
You'll be cc'd twice and .mailmap doesn't have enough information to select your preferred email address.
cheers, Joe
Quoted 25 lines · Joe Perches
Quoted 8 lines · James Bottomley
Quoted 4 lines · Joe Perches
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.
Then change the other entry.
And if you really like your initials, you should probably change the email address format you're using right now and probably the mechanism you use to send your patches and acks as well.
Look at the name I'm replying to: (no quotes)
"James Bottomley <[email protected]>"Right now, if somebody uses get_maintainers.pl on a patch for a file in
drivers/scsi, git will find your signoffs as(no quotes)
"James Bottomley <[email protected]>"
Quoted 7 lines
and the
scripts/get_maintainers.plwill useMAINTAINERSentry of(with quotes)
"James E.J. Bottomley <[email protected]>"You'll be cc'd twice and .mailmap doesn't have enough information to select your preferred email address.
Assuming people blindly use the scripts, rest assured that my email system won't collapse under the weight of the extra cc's.
James