Thread: Re: Time to add a Git .mailmap?

On 2024-Oct-31, Daniel Gustafsson wrote:

> When looking at our Git tree for a recent conference presentation I happened to
> notice that we have recently gained duplicate names in the shortlog.  Not sure
> if we care enough to fix that with a .mailmap, but if we do the attached diff
> makes sure that all commits are accounted for a single committer entry.

LGTM.  I'd also add this line while at it:

Peter Eisentraut <peter@eisentraut.org> <peter_e@gmx.net>

This takes care of all the duplicate "identities" in the history AFAICT.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"No me acuerdo, pero no es cierto.  No es cierto, y si fuera cierto,
 no me acuerdo."                 (Augusto Pinochet a una corte de justicia)

On 01.11.24 12:53, Alvaro Herrera wrote:
> On 2024-Oct-31, Daniel Gustafsson wrote:
> 
>> When looking at our Git tree for a recent conference presentation I happened to
>> notice that we have recently gained duplicate names in the shortlog.  Not sure
>> if we care enough to fix that with a .mailmap, but if we do the attached diff
>> makes sure that all commits are accounted for a single committer entry.
> 
> LGTM.  I'd also add this line while at it:
> 
> Peter Eisentraut <peter@eisentraut.org> <peter_e@gmx.net>
> 
> This takes care of all the duplicate "identities" in the history AFAICT.

I'm not sure if this is a good use of the mailmap feature.  If someone 
commits under <peter@companyfoo.com> for a while and then later as 
<peter@companybar.com>, and the mailmap maps everything to the most 
recent one, that seems kind of misleading or unfair?  The examples on 
the gitmailmap man page all indicate that this feature is to correct 
accidental variations or obvious mistakes, but not to unify everything 
to the extent that it alters the historical record.