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:19 UTC
- Message-ID
- <46a038f91003181419n5d076bdbv18e32e292d7937a8@mail.gmail.com>
- In-Reply-To
- <b4087cc51003181412s78d153c8t48984eb87eb75e0e@mail.gmail.com>
On Thu, Mar 18, 2010 at 5:12 PM, Michael Witten <mfwitten@gmail.com> wrote:
> 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.
What's the value? For me it'll be "Martin Langhoff". I already have that.
> Nothing is being taken away.
But something is added.
Good design is not when there's nothing more to add, it's when there's nothing left _to remove_.
Git is what it is thanks to removing superfluous crud from its core datamodel. Don't be surprised that there is a very strong resistance to adding anything to that datamodel.
> Essentially, the goal is to distribute the task of maintaining aliases.
Already achieved with mailcap. No need to mess with the secret of git's success (the tight datamodel).
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