Re: Time to add a Git .mailmap? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Time to add a Git .mailmap?
Date
Msg-id 013efc76-7c17-4e87-ac1a-b2060cd2e899@eisentraut.org
Whole thread Raw
In response to Re: Time to add a Git .mailmap?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
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.




pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: define pg_structiszero(addr, s, r)
Next
From: 송영욱
Date:
Subject: Inquiry on Future Plans for Enhancements to PostgreSQL MVCC Model and Vacuum Process