Re: Time to add a Git .mailmap?

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Time to add a Git .mailmap?
Date: 2024-11-01 12:53:58
Message-ID: 013efc76-7c17-4e87-ac1a-b2060cd2e899@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)eisentraut(dot)org> <peter_e(at)gmx(dot)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(at)companyfoo(dot)com> for a while and then later as
<peter(at)companybar(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message 송영욱 2024-11-01 12:56:55 Inquiry on Future Plans for Enhancements to PostgreSQL MVCC Model and Vacuum Process
Previous Message Bertrand Drouvot 2024-11-01 12:50:10 Re: define pg_structiszero(addr, s, r)