Re: What's in a name? Let's use a (uuid,name,email) triplet
- From
Michael Witten <mfwitten@gmail.com>
- Date
- Mar 18, 2010, 21:57 UTC
- Message-ID
- <b4087cc51003181457s76560b02y84aafbe77f45af87@mail.gmail.com>
- In-Reply-To
- <46a038f91003181439lc343dafl6b9321a0b620de84@mail.gmail.com>
On Thu, Mar 18, 2010 at 16:39, Martin Langhoff <martin.langhoff@gmail.com> wrote:
Show 10 quoted lines
> On Thu, Mar 18, 2010 at 5:29 PM, Michael Witten <mfwitten@gmail.com> wrote: >> On Thu, Mar 18, 2010 at 16:19, Martin Langhoff >>> What's the value? For me it'll be "Martin Langhoff". I already have that. >> >> Well, that's rather egotistical considering you're probably not the >> only Martin Langhoff in this world. I'd advocate something like >> "Martin Langhoff <martin.langhoff@gmail.com>". > > So you are saying we should change the core datamodel of git to say... > what we already can say?
You see, Martin, you might want/need to stop using "Martin Langhoff <martin.langhoff@gmail.com>" as your email account, but there's no reason why you can't continue to use it for your UUID.
>> At worst, things will be just like they have always been. > > No, we'll have another way to have data mismatches. There are _more_ > moving parts in your model. That's what Linus is pointing out.
Mismatches in UUIDs will be the only thing worth worrying about; fortunately, UUIDs won't change as frequently because they would be rarely typed by git users and they are not subject to changing email systems or changing names.