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

[Michael Witten <mfwitten@gmail.com>]

On Thu, Mar 18, 2010 at 15:44,  <tytso@mit.edu> wrote:
>   Hi, I'm <dd1b51a1-ce2a-41fd-ae89-f68b7f0ace85> and here are the things
>   that you need to fix with your patch....

Look, there is a huge misunderstanding.

This is all that I'm saying: Keep git exactly the way it is, but add
one extra piece of identifying information for each person.

That's it.

Nothing is being taken away.

You can still see/grep/access the full names and email addresses just
as before, only now there will be another piece of information on
which to filter (or ignore it if you want).

In the most general form of my proposal, the idea is to let the user
choose some piece of information that he himself deems to be uniquely
identifying over a long period of time. However, I think it would be
smart to reduce that information to a SHA-1 (at least when it's
recorded in, say, a commit).

Essentially, the goal is to distribute the task of maintaining aliases.