From: Bryan Turner <bturner@atlassian.com>
To: Jeff King <peff@peff.net>
Cc: SURA <surak8806@gmail.com>, Git Users <git@vger.kernel.org>
Subject: Re: I've noticed the command `git --git-dir=<path> shortlog`
Date: Fri, 5 Feb 2021 12:02:03 -0800 [thread overview]
Message-ID: <CAGyf7-EB=J1j1LOUiUBHE+g-hA1WXUNy3F4y84rCRwzGc2zo_A@mail.gmail.com> (raw)
In-Reply-To: <YB148VZJqKIPC8P2@coredump.intra.peff.net>
On Fri, Feb 5, 2021 at 9:28 AM Jeff King <peff@peff.net> wrote:
>
> It's possible somebody is relying on this in order to read ".mailmap" in
> a bare repository, but it seems rather unlikely. And the documentation
> says "If the file .mailmap exists at the toplevel of the repository",
> which I think pretty clearly means the top of the working tree.
There was a time, before the change was made to have bare repositories
read the HEAD:.mailmap blob if one exists, when Bitbucket Server
relied on this in order to have mailmapping. We'd unpack the
`HEAD:.mailmap` blob to `.mailmap` in the bare repository whenever it
changed. Now that it's automatically read out of the repository,
though, that manual unpacking code was removed.
(Not disagreeing with your "seems rather unlikely", by the way. With
the blob reading behavior I think it's probably true.)
Bryan
next prev parent reply other threads:[~2021-02-05 20:07 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 [this message]
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
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
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='CAGyf7-EB=J1j1LOUiUBHE+g-hA1WXUNy3F4y84rCRwzGc2zo_A@mail.gmail.com' \
--to=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--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.
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).