RE: Dealing with corporate email recycling

From: rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date: Mar 13, 2022, 23:23 UTC
Message-ID: <021401d83731$62813630$2783a290$@nexbridge.com>
In-Reply-To: <xmqqtuc1tpdj.fsf@gitster.g>

On March 13, 2022 7:16 PM, Junio C Hamano wrote:

Show 9 quoted lines

>To: Sean Allred <allred.sean@gmail.com>
>Sean Allred <allred.sean@gmail.com> writes:
>
>> rather than use magic comments :-) Adapting to your suggestion, this
>> might look like the following:
>>
>>     A. U. Thor <foo@example.com> <ada.example.com> <[ approxidate ]>
>
>You'd probably want a timerange (valid-from and valid-to), instead of one

single

>timestamp?
>
>Because at least three valid forms of mailmap entries should be understood

by the

Show 7 quoted lines

>current generation of mailmap readers, i.e.
>
>    Human Readable Name <e-mail@add.re.ss>
>    Right Name <right@add.re.ss> <wrong@add.re.ss>
>    Right Name <right@add.re.ss> Wrong Name <wrong@add.re.ss>
>
>the extended entry format to record the validity timerange should be chosen

to

>cause parsers that are prepared to take these three kinds of lines to barf

and

>ignore.

Could we not use SSH's ssh-keygen -V for this purpose when establishing persistent identities independent of user/email? We already do this for signed commits.