From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@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:02 -0700 [thread overview]
Message-ID: <20080801154902.c60717e5.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0808011534260.6819@nehalem.linux-foundation.org>
On Fri, 1 Aug 2008 15:39:37 -0700 (PDT) Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> Btw, the real issue here is
>
> - why do you want to make things uglier and make up stupid rules that are
> irrelevant to git, just for something that you admit you hadn't ever
> even _noticed_ until now, and now that you know about it it's not even
> a problem any more?
None of that is correct.
The real issue here is:
- Why do you want to take usable RFC-compliant email addresses and
mangle them in a manner which still doesn't match the person's
actual name and which makes unsuspecting users of git potentially
lose important email communications?
Ain't framing great?
> especially as
>
> - we know people won't do the quoting _anyway_, since we actually have
> tons of examples of that in the kernel as-is.
>
> Quoting should be for _tools_, not for people. And even if we did it, we
> probably wouldn't be fully rfc2822-compliant anyway, because anybody sane
> would decide to not quote '@' and '.', rigth?
>
> Because those don't actually really have special meaning (yeah, they are
> "special" characters in rfc-2822, but nobody cares, and the MUA can do it
> for us, no)?
>
> So now we'd actually not really be rfc-compliant _anyway_, because
> everybody really realizes just how annoying that would really be.
>
Linus, just admit it: copying and pasting from git-log output into the MUA
is *useful*. And you've made it less reliable.
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
2008-08-04 20:14 ` Karl Hasselström
2008-08-01 22:39 ` Linus Torvalds
2008-08-01 22:49 ` Andrew Morton [this message]
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=20080801154902.c60717e5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.org \
--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).