From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Jeff King <peff@peff.net>, Bryan Turner <bturner@atlassian.com>,
SURA <surak8806@gmail.com>, Git Users <git@vger.kernel.org>
Subject: Re: [PATCH] mailmap: only look for .mailmap in work tree
Date: Tue, 09 Feb 2021 14:16:40 -0800 [thread overview]
Message-ID: <xmqq5z30zy2f.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAPig+cSdTCYV=2OMEZTqahrfBypaHeD40ToMFJ1zbRNpkiPbYw@mail.gmail.com> (Eric Sunshine's message of "Tue, 9 Feb 2021 14:00:37 -0500")
Eric Sunshine <sunshine@sunshineco.com> writes:
> On Tue, Feb 9, 2021 at 12:31 PM Jeff King <peff@peff.net> wrote:
>> Subject: [PATCH] mailmap: only look for .mailmap in work tree
>> [...]
>> Signed-off-by: Jeff King <peff@peff.net>
>> ---
>> diff --git a/Documentation/git-shortlog.txt b/Documentation/git-shortlog.txt
>> @@ -113,6 +113,10 @@ MAPPING AUTHORS
>> +Note that if `git shortlog` is run outside of a repository (to process
>> +log contents on stdin), it will look for a `.mailmap` file in the
>> +current directory.
>
> Elsewhere in this same document, techy-jargon "stdin" is spelled out
> fully as "standard input".
Good point.
next prev parent reply other threads:[~2021-02-09 22:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 3:05 I've noticed the command `git --git-dir=<path> shortlog` SURA
2021-02-05 16:57 ` Jeff King
2021-02-05 20:02 ` Bryan Turner
2021-02-09 17:29 ` [PATCH] mailmap: only look for .mailmap in work tree Jeff King
2021-02-09 19:00 ` Eric Sunshine
2021-02-09 22:16 ` Junio C Hamano [this message]
2021-02-10 16:05 ` Jeff King
2021-02-09 21:23 ` Junio C Hamano
2021-02-10 16:15 ` Jeff King
2021-02-10 20:10 ` Junio C Hamano
2021-02-10 20:31 ` Jeff King
2021-02-10 20:34 ` Jeff King
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=xmqq5z30zy2f.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.com \
--cc=surak8806@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 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).