git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 16:16:39 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0808011608150.6819@nehalem.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0808011554350.6819@nehalem.linux-foundation.org>



On Fri, 1 Aug 2008, Linus Torvalds wrote:
>
> That's my argument here. Life is tough.  Not everthing is going to be 
> easy. Your solution would "work", but it would be a horrid piece of crap.

..and I really think that the

	"=?utf-8?q?S=2E=C3=87a=C4=9Flar?= Onur" <caglar@pardus.org.tr>

example should be the one that makes you say "Ok, you're right".

The undeniable fact is, if we kept things in that format, even your broken 
mailer wouldn't have corrupted it. You could cut-and-paste things, and 
they's show up correctly at the other end, regardless of whether the 
problem is with your mailer or with the cut-and-paste, or anything else.

So clearly, "=?utf-8?q?S=2E=C3=87a=C4=9Flar?= Onur" _must_ be the superior 
format that git should have used, no?

Because clearly that is the most automation-friendly thing that _never_ 
requires anybody to think at all, and you can cut-and-paste it between 
programs without ever having to worry about anything at all. No special 
characters, no special meanings, no need to worry about limitations of 
implementation.

So the fact that git completely FUCKS IT UP, and when you do 'git log' git 
will have corrupted this to

	Author: S.Çağlar Onur <caglar@pardus.org.tr>

is clearly git doing the wrong thing. Right?

WRONG.

The fact is, git does the right thing. And yes, it means that you cannot 
just blindly cut-and-paste. And yes, it means that your mailer actually 
has to work right for you to even -see- the right email address. And yes, 
it means that any number of things can screw up, and corrupt it.

But it is STILL the right thing. Because what matters more than your 
ability to cut-and-paste or anything like that is  the fact that we should 
make things look sane.

The thing is, you can actually get git to output the crazy names. Just do

	git show --pretty=email 37a4c940749670671adab211a2d9c9fed9f3f757

and now you get the email-prettified thing for at least the author. No, 
git won't corrupt the actual message, so the Signed-off-by: lines will 
still show Çağlar's first name, but you can actually get back that odd 
format.

(In fact, --pretty=email will do it as

	From: =?utf-8?q?S.=C3=87a=C4=9Flar=20Onur?= <caglar@pardus.org.tr>

which is admittedy _even_uglier_, but whatever.. The difference between 
really f*cking ugly and really f*cking uglier is not really relevant).

			Linus

  reply	other threads:[~2008-08-01 23:19 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 [this message]
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.0808011608150.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).