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

[PATCH] Describe how to generate .mailmap automatically using "git log"

From
EHEric Hanchrow <erich@cozi.com>
Date
Apr 22, 2009, 17:40 UTC
Message-ID
<70F0BA8D5F15094CBC8B7F2E4BBCD9B52772BF72@corp-mail-1>
---
 Documentation/mailmap.txt |   10 ++++++++++
 1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/Documentation/mailmap.txt b/Documentation/mailmap.txt
index 288f04e..ae62669 100644
--- a/Documentation/mailmap.txt
+++ b/Documentation/mailmap.txt
@@ -72,3 +72,13 @@ Santa Claus <santa.claus@northpole.xx> <me@company.xx>

 Use hash '#' for comments that are either on their own line, or after
 the email address.
+
+If most of your commits lack proper author names (as will be the case
+if your repository was generated by linkgit:git-svn[1]), you can
+generate most of a correct `.mailmap` automatically like this:
+
+------------
+git log "--pretty=%an <%ae>" | sort | uniq > .mailmap
+------------
+
+You will then have to edit the file to add the proper author names.
--
1.6.3.rc0.146.gd07d5
Message 1 of 1 in “Describe how to generate .mailmap automatically using "git log"”
  1. Describe how to generate .mailmap automatically using "git log"Eric Hanchrow, Apr 22, 2009

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.