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

Re: [PATCH 1/1] mailmap: support hashed entries in mailmaps

From
Johannes Sixt <j6t@kdbg.org>
Date
Dec 13, 2020, 09:45 UTC
Message-ID
<b297b843-99e1-152d-aed1-20371af42d42@kdbg.org>
In-Reply-To
<2cc4925f-3661-1dfb-2668-5f56edcb8455@kdbg.org>
Am 13.12.20 um 10:34 schrieb Johannes Sixt:
Show 10 quoted lines
> I don't understand the concept. A mailmap entry of the form
> 
>    A <a@b> <x@y>
> 
> tells that the former address <x@y>, which is recorded in old project
> history, should be replaced by A <a@b> when a commit is displayed. I am
> assuming that the idea is that old <x@y> should be the "banned" address.
> How does a hashed entry help when the hashed value appears at the right
> side of a mailmap entry and that literal string never appears anywhere
> in the history?

Never mind, I got it: A wants to be disassociated from <x@y>, but not from their contributions whose authorship was recorded as <x@y>. Therefore, Git must always compute the hash of all of <x@y>, <a@b>, etc, just in case that the hashed form appears anywhere in the mailmap file.

-- Hannes
Previous: Johannes SixtNext: brian m. carlson
Message 4 of 14 in “Hashed mailmap support”
  1. 0/1 Hashed mailmap supportbrian m. carlson, Dec 13, 2020
  2. 1/1 mailmap: support hashed entries in mailmapsbrian m. carlson, Dec 13, 2020
  3. Johannes SixtDec 13, 2020
  4. Johannes SixtDec 13, 2020
  5. brian m. carlsonDec 13, 2020
  6. Junio C HamanoDec 14, 2020
  7. brian m. carlsonDec 16, 2020
  8. Ævar Arnfjörð BjarmasonDec 14, 2020
  9. Phillip WoodDec 15, 2020
  10. Jeff KingDec 15, 2020
  11. Jeff KingDec 15, 2020
  12. Phillip WoodDec 15, 2020
  13. brian m. carlsonDec 18, 2020
  14. Jeff KingDec 18, 2020

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.