git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Stefan Beller <sbeller@google.com>,
	bwilliamseng@gmail.com, git <git@vger.kernel.org>,
	bwilliams.eng@gmail.com
Subject: Re: [PATCH] mailmap: update brandon williams's email address
Date: Fri, 18 Jan 2019 11:57:54 -0500	[thread overview]
Message-ID: <20190118165754.GA11350@sigill.intra.peff.net> (raw)
In-Reply-To: <20181207222225.GC73340@google.com>

On Fri, Dec 07, 2018 at 02:22:25PM -0800, Jonathan Nieder wrote:

> Stefan Beller wrote:
> 
> > What would be more of interest is why we'd be interested in this patch
> > as there is no commit/patch sent by Brandon with this email in gits history.
> 
> I think there's an implicit assumption in this question that isn't
> spelled out.  Do I understand correctly that you're saying the main
> purpose of .mailmap is to figure out whether two commits are by the
> same author?
> 
> My own uses of .mailmap primarily have a different purpose: to find
> out the preferred contact address for the author of a given commit.

I just had to cc Brandon and manually look up his email address, which
made me wonder what ever happened to this patch. :)

FWIW, I also use mailmap to find contact email addresses, with:

  $ git help who
  'who' is aliased to '!sh -c 'git --no-pager log -1 --format="%an <%aE>" --author="$1" -i' -'

So lacking another such registry, I'd like to add my support for using
mailmap for this purpose.

-Peff

  reply	other threads:[~2019-01-18 16:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 20:56 [PATCH] mailmap: update brandon williams's email address Brandon Williams
2018-12-07 21:40 ` Jonathan Nieder
2018-12-07 22:11   ` Stefan Beller
2018-12-07 22:22     ` Jonathan Nieder
2019-01-18 16:57       ` Jeff King [this message]
2019-01-18 18:16         ` Junio C Hamano
2019-01-18 18:38           ` Jeff King
2018-12-08  6:08     ` Junio C Hamano
2018-12-08  6:51       ` Brandon Williams
2018-12-10  8:36         ` Johannes Schindelin
2018-12-08  8:25       ` Duy Nguyen
2018-12-08 12:18       ` Ævar Arnfjörð Bjarmason

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=20190118165754.GA11350@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=bwilliams.eng@gmail.com \
    --cc=bwilliamseng@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=sbeller@google.com \
    /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;
as well as URLs for NNTP newsgroup(s).