From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: email address handling
Date: Fri, 1 Aug 2008 14:12:04 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808011356560.3277@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20080801135421.5ca0f6af.akpm@linux-foundation.org>
On Fri, 1 Aug 2008, Andrew Morton wrote:
>
> Well, what I'm saying is that it was an incorrect design decision.
And I'm saying that I disagree.
> Yesterday, I copied and pasted what _looked_ like a usable
> name+email-address from some git output and into an MUA. Unlike the
> thousands of preceding times, it did not work.
>
> I think it was reasonable of me to assume that it would work. Blaming
> the surprised and misled user for not understanding some earlier
> internal design decision didn't satisfy him!
>
> True story! From a user.
Hey, there are tons of surprises in life. Users make mistakes and
assumptions that turn out to not be true. If you think you can avoid all
such issues, I think you aren't living in the real world.
You'll be shocked to hear that even the so-called _email_ address isn't
necessarily valid at all at times. Look closer, and you'll find email
addresses that don't work at all. It turns out that if you don't set it
explicitly, git will guess, and sometimes the end result won't actually
work as an email address.
Beign surprised and then saying "I was surprised, so the whole design is
broken" - that's a very silly standpoint to make. I suggest you
reconsider. How many times have you had people "surprised" by correct
kernel behaviour? Happens all the time.
Do you think they are all indicative of bad design, or maybe just "welcome
to the real world - your preconceived notions didn't turn out to be
accurate after all"?
It's a design decision to show the name as readably as possible. One that
I think was correct.
Linus
next prev parent reply other threads:[~2008-08-01 21:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 2:40 email address handling Andrew Morton
2008-08-01 19:34 ` Linus Torvalds
2008-08-01 19:45 ` Andrew Morton
2008-08-01 19:56 ` Linus Torvalds
2008-08-01 20:07 ` Junio C Hamano
2008-08-01 20:11 ` Andrew Morton
2008-08-01 20:17 ` Linus Torvalds
2008-08-01 20:24 ` Andrew Morton
2008-08-01 20:40 ` Linus Torvalds
2008-08-01 20:41 ` Linus Torvalds
2008-08-01 20:54 ` Andrew Morton
2008-08-01 21:12 ` Linus Torvalds [this message]
2008-08-01 21:16 ` Johannes Schindelin
2008-08-01 21:25 ` Junio C Hamano
2008-08-02 11:03 ` Johannes Schindelin
2008-08-01 21:50 ` Junio C Hamano
2008-08-01 21:58 ` Andrew Morton
2008-08-01 22:15 ` Theodore Tso
2008-08-01 22:27 ` Andrew Morton
2008-08-01 22:34 ` Linus Torvalds
2008-08-01 22:44 ` Andrew Morton
2008-08-01 22:52 ` Linus Torvalds
2008-08-01 23:00 ` Andrew Morton
2008-08-01 22:49 ` Linus Torvalds
2008-08-04 20:14 ` Karl Hasselström
2008-08-01 22:39 ` Linus Torvalds
2008-08-01 22:49 ` Andrew Morton
2008-08-01 22:55 ` Linus Torvalds
2008-08-01 23:16 ` Linus Torvalds
2008-08-02 11:31 ` Johannes Schindelin
2008-08-02 16:20 ` Linus Torvalds
2008-08-02 16:36 ` Junio C Hamano
2008-08-02 16:59 ` Johannes Schindelin
2008-08-02 17:08 ` Linus Torvalds
2008-08-02 16:40 ` Junio C Hamano
2008-08-02 16:42 ` Junio C Hamano
2008-08-02 17:50 ` Junio C Hamano
2008-08-01 22:23 ` Linus Torvalds
2008-08-01 22:41 ` Andrew Morton
2008-08-01 20:00 ` Junio C Hamano
2008-08-01 20:14 ` Andrew Morton
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=alpine.LFD.1.10.0808011356560.3277@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=git@vger.kernel.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).