From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Theodore Tso <tytso@mit.edu>, Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: email address handling
Date: Fri, 1 Aug 2008 15:49:43 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808011543500.6819@nehalem.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0808011531290.6819@nehalem.linux-foundation.org>
On Fri, 1 Aug 2008, Linus Torvalds wrote:
>
> S.Çağlar Onur <caglar@pardus.org.tr>
Btw, poor guy is _really_ screwed. He'd show up as
"=?utf-8?q?S=2E=C3=87a=C4=9Flar?= Onur" <caglar@pardus.org.tr>
which must really hurt.
Can you not see how STUPID it would be to say that the name should be
shown as an email encoding requires it?
Really. Just admit that you were wrong. The fact is, asking for rfc2822
encoding in logs etc is a HORRIBLY HORRIBLY stupid thing to do.
What you really want was just something you could cut-and-paste into your
mailer. Which actually means that the only special character is probably
",", and your claims of how bad the design was that it didn't leave the
total mess that rfc2822 is was actually not true, and was based on simply
not knowing how nasty the real world is...
Quote frankly, If I had one of the Finnish special characters in my name,
I'd piss on your grave if you suggested that. Try to guess what something
like
=?ISO-8859-15?Q?Linus_T=F6rnqvist?= <torvalds@linux-foundation.org>
is supposed to be.
Linus
next prev parent reply other threads:[~2008-08-01 22:51 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
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 [this message]
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.0808011543500.6819@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tytso@mit.edu \
/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).