Re: What's in a name? Let's use a (uuid,name,email) triplet
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Mar 18, 2010, 21:39 UTC
- Message-ID
- <46a038f91003181439lc343dafl6b9321a0b620de84@mail.gmail.com>
- In-Reply-To
- <b4087cc51003181429v2998b95ei3f08360e6d2a5aa7@mail.gmail.com>
On Thu, Mar 18, 2010 at 5:29 PM, Michael Witten <mfwitten@gmail.com> wrote:
Show 6 quoted lines
> 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?
> 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.
This is a case where an ancillary "fixup table", in the form of mailmap, works best. Don't move the fixup table to the core of the datamodel, it just doesn't belong there.
Here's a hint: using your "uuid" model, I'll get some commits into a project with the wrong uuid. Because I made a typo, or changed machines (and a random uuid got created), whatever reason. So now in my project I appear under 2 uuids.
What should we do in that case? Use mailmap to map the stray uuid to the "real" one?... Have we done a lot of work to get back to square 0?
cheers,
m
-- martin.langhoff@gmail.com martin@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff