From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: email address handling
Date: Fri, 1 Aug 2008 15:23:23 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808011507430.6819@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20080801145804.85041bbd.akpm@linux-foundation.org>
On Fri, 1 Aug 2008, Andrew Morton wrote:
>
> I preserve the quotes (when present) in signoffs for this exact reason.
You must be one of the few ones. According to the RFC's, you should quote
pretty much any punctuation mark, including "." itself. Which means that
things like
Signed-off-by: David S. Miller <davem@davemloft.net>
should be quoted if they were email addresses.
That would be very irritating.
It's even _more_ irritating for things like D'Souza (or Giuseppe D'Eliseo
to take a real example from the kernel). For David, we could just not use
the "S." - for others, the special characters are very much part of the
name. It would also be very irritating for important messages like
Signed-off-by: Linus "I'm a moron" Torvalds <torvalds@osdl.org>
etc, where it sure as heck isn't a rfc2822-compliant email address.
So the thing is, "strict email format" is just very annoying. Git does
know how to do (well, it _should_) it for "git send-email", but making the
human-readable output ugly just because somebody might want to
cut-and-paste it sounds really sad.
You could cut-and-paste just the stuff inside the angle branckets, though.
That should work.
Linus
next prev parent reply other threads:[~2008-08-01 22:24 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
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 [this message]
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.0808011507430.6819@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).