From: Jon Smirl <jonsmirl@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michael Witten <mfwitten@gmail.com>, git@vger.kernel.org
Subject: Re: What's in a name? Let's use a (uuid,name,email) triplet
Date: Thu, 18 Mar 2010 15:16:43 -0400 [thread overview]
Message-ID: <9e4733911003181216m59a09ad6y6c7c890714d0d20b@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1003181203370.18017@i5.linux-foundation.org>
On Thu, Mar 18, 2010 at 3:07 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> 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 happen to think that the concept of privacy and working on an open
source project are fairly incompatible. But apparently their are
people who think otherwise. The use would be to reconstruct that
mailmap I made, but with the email addresses replaced with SHA1 hashes
of the email. No human would use the SHA1s, they're just there to
obscure the emails.
>
> 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
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2010-03-18 19:23 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 13:23 What's in a name? Let's use a (uuid,name,email) triplet Michael Witten
2010-03-18 13:48 ` Jon Smirl
2010-03-18 14:26 ` Michael Witten
2010-03-18 17:27 ` Linus Torvalds
2010-03-18 19:02 ` Jon Smirl
2010-03-18 19:07 ` Linus Torvalds
2010-03-18 19:16 ` Jon Smirl [this message]
2010-03-18 19:20 ` Linus Torvalds
2010-03-18 19:37 ` Jon Smirl
2010-03-18 19:47 ` Linus Torvalds
2010-03-18 19:50 ` Linus Torvalds
2010-03-18 20:01 ` Linus Torvalds
2010-03-19 19:39 ` Junio C Hamano
2010-03-18 20:31 ` Reece Dunn
2010-03-18 20:59 ` Linus Torvalds
2010-03-18 19:32 ` Michael Witten
2010-03-18 19:40 ` Linus Torvalds
2010-03-18 19:47 ` Michael Witten
2010-03-18 19:52 ` Linus Torvalds
2010-03-18 20:00 ` Michael Witten
2010-03-18 19:52 ` Wincent Colaiuta
2010-03-18 19:40 ` Wincent Colaiuta
2010-03-18 19:42 ` Martin Langhoff
2010-03-18 22:36 ` Martin Langhoff
2010-03-18 23:17 ` Nicolas Pitre
2010-03-18 23:26 ` Jon Smirl
2010-03-18 23:34 ` Nicolas Pitre
2010-03-18 23:41 ` Jon Smirl
2010-03-18 23:58 ` Nicolas Pitre
2010-03-19 0:16 ` Jon Smirl
2010-03-19 0:17 ` Linus Torvalds
2010-03-19 0:39 ` Jon Smirl
2010-03-19 0:50 ` Linus Torvalds
2010-03-19 1:12 ` Jon Smirl
2010-03-19 1:45 ` Nicolas Pitre
2010-03-19 2:05 ` Jon Smirl
2010-03-18 23:34 ` Michael Witten
2010-03-18 18:42 ` Michael Witten
2010-03-18 18:47 ` Matthieu Moy
2010-03-18 18:57 ` Michael Witten
2010-03-18 19:12 ` Nicolas Pitre
2010-03-18 20:44 ` tytso
2010-03-18 21:12 ` Michael Witten
2010-03-18 21:19 ` Martin Langhoff
2010-03-18 21:29 ` Michael Witten
2010-03-18 21:39 ` Martin Langhoff
2010-03-18 21:46 ` Michael Witten
2010-03-18 21:55 ` Martin Langhoff
2010-03-18 22:02 ` Michael Witten
2010-03-18 23:37 ` Nicolas Pitre
2010-03-18 23:44 ` Michael Witten
2010-03-19 0:03 ` Nicolas Pitre
2010-03-19 0:27 ` Michael Witten
2010-03-19 0:32 ` Nicolas Pitre
2010-03-18 22:06 ` Reece Dunn
2010-03-18 21:57 ` Michael Witten
2010-03-19 12:34 ` Paolo Bonzini
2010-03-19 12:43 ` Michael Witten
2010-03-19 12:53 ` Paolo Bonzini
2010-03-19 13:03 ` Michael Witten
2010-03-19 13:08 ` Paolo Bonzini
2010-03-19 13:13 ` Michael Witten
2010-03-19 13:41 ` Wincent Colaiuta
2010-03-19 13:59 ` Michael Witten
2010-03-19 14:13 ` Martin Langhoff
2010-03-18 21:27 ` Linus Torvalds
2010-03-18 21:44 ` Michael Witten
2010-03-18 23:12 ` Jon Smirl
2010-03-18 22:17 ` A Large Angry SCM
2010-03-19 2:47 ` Sitaram Chamarty
2010-03-19 5:17 ` Nazri Ramliy
2010-03-19 8:41 ` Michael Haggerty
2010-03-19 11:39 ` Michael Witten
2010-03-19 11:45 ` david
2010-03-19 11:54 ` Mike Hommey
2010-03-19 12:09 ` Reece Dunn
2010-03-19 12:16 ` Michael Witten
2010-03-19 12:18 ` Michael Witten
2010-03-19 14:57 ` Reece Dunn
2010-03-19 15:26 ` Michael J Gruber
2010-03-19 16:05 ` david
2010-03-19 17:16 ` Michael Witten
2010-03-19 12:25 ` Jon Smirl
2010-03-19 12:40 ` Reece Dunn
2010-03-19 12:09 ` Michael Witten
2010-03-22 12:06 ` Mark Brown
2010-03-22 14:38 ` Michael Witten
2010-03-24 19:18 ` Erik Faye-Lund
2010-03-24 19:23 ` Michael Witten
2010-03-19 12:08 ` Michael Witten
2010-03-19 14:08 ` Michael Haggerty
2010-03-19 17:02 ` david
2010-03-19 17:06 ` Michael Witten
2010-03-24 18:50 ` Avi Kivity
2010-03-19 14:08 ` Jakub Narebski
2010-03-19 14:33 ` Jon Smirl
2010-03-19 14:52 ` Michael J Gruber
2010-03-19 14:40 ` Michael Witten
2010-03-19 14:56 ` Erik Faye-Lund
2010-03-19 15:05 ` Michael Witten
2010-03-19 15:12 ` Michael Witten
2010-03-19 15:25 ` Erik Faye-Lund
2010-03-19 15:12 ` Reece Dunn
2010-03-20 0:21 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e4733911003181216m59a09ad6y6c7c890714d0d20b@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=mfwitten@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).