From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH v2] mailmap: update brian m. carlson's email address
Date: Wed, 9 May 2018 00:19:57 +0000 [thread overview]
Message-ID: <20180509001957.GE275488@genre.crustytoothpaste.net> (raw)
In-Reply-To: <184451b4-1b34-c1f7-f9b1-0dfa63ab9506@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
On Tue, May 08, 2018 at 10:34:58AM +0530, Kaartic Sivaraam wrote:
> Just to be sure, you're meaning the use of `git log --use-mailmap` when
> you mean `git log` in the log message. Am I right? Or did you mean `git
> shortlog` ?
>
> I'm asking this because I think the `git log` output doesn't consider
> the mailmap file by default.
Correct, it doesn't. In my case, I was using --pretty='%aN <%aE>',
which is how I noticed it in the first place.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 867 bytes --]
next prev parent reply other threads:[~2018-05-09 0:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 23:24 [PATCH] mailmap: update brian m. carlson's email address brian m. carlson
2018-05-07 3:37 ` Junio C Hamano
2018-05-07 19:25 ` Stefan Beller
2018-05-07 23:53 ` brian m. carlson
2018-05-07 23:44 ` brian m. carlson
2018-05-08 1:58 ` [PATCH v2] " brian m. carlson
2018-05-08 3:21 ` Junio C Hamano
2018-05-08 5:04 ` Kaartic Sivaraam
2018-05-09 0:19 ` brian m. carlson [this message]
2018-05-09 7:03 ` Kaartic Sivaraam
2018-05-10 23:13 ` brian m. carlson
2018-05-22 22:08 ` Jonathan Nieder
2018-05-22 22:42 ` brian m. carlson
2018-09-17 18:18 ` [PATCH] mailmap: consistently normalize brian m. carlson's name Jonathan Nieder
2018-09-17 22:21 ` brian m. carlson
2018-09-24 17:39 ` [PATCH v2] " Jonathan Nieder
2018-09-25 1:15 ` brian m. carlson
2018-09-25 2:13 ` Jonathan Nieder
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=20180509001957.GE275488@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.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 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.