Re: What's in a name? Let's use a (uuid,name,email) triplet
- From
- david@lang.hm <david@lang.hm>
- Date
- Mar 19, 2010, 17:02 UTC
- Message-ID
- <alpine.DEB.2.00.1003190959410.10411@asgard.lang.hm>
- In-Reply-To
- <4BA3855A.1070005@alum.mit.edu>
On Fri, 19 Mar 2010, Michael Haggerty wrote:
Show 22 quoted lines
> Michael Witten wrote: >> On Fri, Mar 19, 2010 at 02:41, Michael Haggerty <mhagger@alum.mit.edu> wrote: >>> Michael Witten wrote: >>>> Rather than use a (name,email) pair to identify people, let's use >>>> a (uuid,name,email) triplet. >>>> [...] >>> A UUID doesn't need to be a big hex number. All it has to be is a >>> "Universally Unique Identifier". Like, oh, for example, your >>> >>> *** EMAIL ADDRESS *** >>> >>> [1]. There is even already a way to fix up mistakes or unavoidable >>> email address changes, namely the .mailmap file. >> >> *facepalm* >> >> You've just repeated everything that I've said; go look at the rest of >> the thread, where I spend plenty of time correcting the same hangups >> about my choice of the word UUID and my use of hex digits. > > No, my point is to use the *existing* email address as the UUID > *without* adding another field. Nothing needs to be changed!
if you are now proposing using the e-mail address, that already exists and is supported by the tools, it sounds like you are just withdrawing your proposal (other than possibly proposing that the e-mail field gets renamed to UUID????)
David Lang