Re: What's in a name? Let's use a (uuid,name,email) triplet

> On Fri, Mar 19, 2010 at 10:08 AM, Jakub Narebski <jnareb@gmail.com> wrote:
>> Michael Witten <mfwitten@gmail.com> writes:
>>
>>> Short Version:
>>> -------------
>>>
>>>
>>> Rather than use a (name,email) pair to identify people, let's use
>>> a (uuid,name,email) triplet.
>>>
>>> The uuid can be any piece of information that a user of git determines
>>> to be reasonably unique across space and time and that is intended to
>>> be used by that user virtually forever (at least within a project's
>>> history).
>>>
>>> For instance, the uuid could be an OSF DCE 1.1 UUID or the SHA-1 of
>>> some easily remembered, already reasonably unique information.
>>
>> ... or 'canonical-name canonical-email' pair.
>>
>>>
>>> This could really help keep identifications clean, and it is rather
>>> straightforward and possibly quite efficient.
>>>
>>>
>>> Long Version:
>>> ------------
>> [...]
>>
>>> While git's use of (name,email) pairs to identify each person is
>>> extremely practical, it turns out that it's rather `unstable';
>>
>> This is non-solution to non-problem.
>>
>> First, the user.name and user.email does not need to be name and email
>> from some email account.  It might be some "canonical name" and
>> "canonical email".
>>
>> Second, there are (I think) two main sources of 'unstability' in
>> (name,email) pairs, namely A) misconfigured git (when fetching/pushing
>> using git itself), B) wrong name in email etc. (when sending patches
>> via email, 80% of patches in Linux kernel case).
> 
> Another top source is mangling of non-ASCII charsets when they go
> though the email system. Are the git work flow tools safe for
> alternative charsets? Do the email tools look at the charset header of
> the email message? Check people's names in the kernel commits and
> you'll find lots of examples of this type of mangling.
>