The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: 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:11:03 -0700	[thread overview]
Message-ID: <1249333863.5149.58.camel@Joe-Laptop.home> (raw)
In-Reply-To: <1249332233.3943.211.camel@mulgrave.site>

On Mon, 2009-08-03 at 20:43 +0000, 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.

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 <James.Bottomley@HansenPartnership.com>"

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 <James.Bottomley@HansenPartnership.com>"

and the scripts/get_maintainers.pl will use MAINTAINERS entry of

(with quotes)
	"James E.J. Bottomley <James.Bottomley@HansenPartnership.com>"

You'll be cc'd twice and .mailmap doesn't have enough information
to select your preferred email address.

cheers, Joe


  parent reply	other threads:[~2009-08-03 21:12 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
2009-08-03 21:22     ` Frans Pop
2009-08-03 22:03       ` H. Peter Anvin
2009-08-03 21:11   ` Joe Perches [this message]
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=1249333863.5149.58.camel@Joe-Laptop.home \
    --to=joe@perches.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox