git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Use of a mailmap file with git-log

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 10, 2012, 20:05 UTC
Message-ID
<7vk3spad0k.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CALWbr2ydMkR_O-Gev7k-HjGadRJMv0UH3XdqtM0Jt=vC82GwJw@mail.gmail.com>
Antoine Pelisse <apelisse@gmail.com> writes:
> Yet I'm afraid it could be:
> 1. expensive to rewrite all commit log (reallocating the buffer)
> 2. Inappropriate to change the value in function that is supposed to
> read

In my suggestion I avoided rewriting the log buffer, primarily because of #2 (in addition to "read" cleanliness, such a change may break the gpg signature checking for merges).

We do reencode the contents before we write it out when "encoding" is present, so logically such a rewrite of authors and committers belongs to where that happens, in pretty_print_commit(). Note that this existing rewrite is not done to the commit log buffer but is to a separate buffer meant to be used only for output.

Previous: Antoine PelisseNext: Junio C Hamano
Message 5 of 6 in “Use of a mailmap file with git-log”
  1. Rich MidwinterDec 10, 2012
  2. Junio C HamanoDec 10, 2012
  3. Junio C HamanoDec 10, 2012
  4. Antoine PelisseDec 10, 2012
  5. Junio C HamanoDec 10, 2012
  6. Junio C HamanoDec 10, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.