Re: What's in a name? Let's use a (uuid,name,email) triplet
- From
Linus Torvalds <torvalds@linux-foundation.org>
- Date
- Mar 18, 2010, 19:07 UTC
- Message-ID
- <alpine.LFD.2.00.1003181203370.18017@i5.linux-foundation.org>
- In-Reply-To
- <9e4733911003181202h23b3d702xce8fc0670a994d52@mail.gmail.com>
On Thu, 18 Mar 2010, Jon Smirl wrote:
> > We could hash people emails and then build a .mailmap equivalent thus > hiding their identity.
So? Why? What's the advantage?
I literally _only_ see disadvantages to the whole thing. If the uuid has some meaning (ie it's related to actual _real_ information), then it is nothing but a really inconvenient placeholder for the real information, adn another source of new problems (like "how do we know they are in sync? I edit the .gitconfig file by hand all the time").
And if it doesn't have meaning, then it's just annoying and will never ever be attached to anything relevant long-term.
Either way, there are only downsides, no upsides. There is absolutely _no_ way that teh uuid would ever actually encode any real meaningful information that isn't better represented by the name/email.
Linus