From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stefan Beller <sbeller@google.com>,
Jonathan Nieder <jrnieder@gmail.com>,
bwilliamseng@gmail.com, git <git@vger.kernel.org>,
bwilliams.eng@gmail.com
Subject: Re: [PATCH] mailmap: update brandon williams's email address
Date: Sat, 08 Dec 2018 13:18:44 +0100 [thread overview]
Message-ID: <87sgz8xlcr.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqq5zw48s9q.fsf@gitster-ct.c.googlers.com>
On Sat, Dec 08 2018, Junio C Hamano wrote:
> Stefan Beller <sbeller@google.com> writes:
>
>> On Fri, Dec 7, 2018 at 1:40 PM Jonathan Nieder <jrnieder@gmail.com> wrote:
>>>
>>> Brandon Williams wrote:
>>>
>>> > Signed-off-by: Brandon Williams <bwilliams.eng@gmail.com>
>>> > ---
>>> > .mailmap | 1 +
>>> > 1 file changed, 1 insertion(+)
>>>
>>> I can confirm that this is indeed the same person.
>>
>> 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.
>
> Once I "git am" the message that began this thread, there will be a
> commit under this new ident, so that would be somewhat a moot point.
"Get to the top of 'git shortlog -sn' with this one easy trick" :)
(The patch makes sense, good to see you back on-list Brandon)
prev parent reply other threads:[~2018-12-08 12:18 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
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 [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgz8xlcr.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=bwilliams.eng@gmail.com \
--cc=bwilliamseng@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).