From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jeff King <peff@peff.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
V?in? J?rvel? <v@pp.inet.fi>,
git@vger.kernel.org
Subject: Re: [PATCH] git-gui: Added support for OS X right click
Date: Sat, 4 Aug 2007 09:37:17 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0708040928350.5037@woody.linux-foundation.org> (raw)
In-Reply-To: <20070804071131.GA6557@coredump.intra.peff.net>
On Sat, 4 Aug 2007, Jeff King wrote:
>
> On Sat, Aug 04, 2007 at 02:55:16AM -0400, Shawn O. Pearce wrote:
>
> > V??in?? J??rvel?? <v@pp.inet.fi> wrote:
>
> Your mailer claims this message is in us-ascii, but I think it isn't...
Actually, the email claims it was iso-latin1, at least here. Which the
*body* of the email apparently really was.
However (and this is a pretty common thing), the *headers* are
unspecified, and a lot of email clients seem to think that if that
happens, they default to US-ASCII and think that those iso-latin1
characters are crud.
Which is a damn shame. "alpine" does this, and it irritates me no end. I
see emails where I can read the body fine, but it shows '????' for subject
lines and authors even though it's the exact same character set.
Stupid, stupid, stupid.
Dammit, if the thing says
Content-type: text/plain; charset=ISO-8859-1; format=flowed
(which it did), then yes, by some idiotic reading of the RFC's that
probably only affects the body of the email. But those headers (and the
"From:" line in particular) were *also* in ISO-8859-1, and email clients
should default to using the same character set unless something else is
said.
Btw, I suspect git "mailsplit" gets this wrong too. I rant and rave, but
in the end, I solved it by just having the code guess sanely (commit
b59d398beab604e577846ef8393735478c1ca3c2 makes things come out right in
practice, regardless) instead of trying to do something "technically
correct".
Linus
next prev parent reply other threads:[~2007-08-04 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 9:27 [PATCH] git-gui: Added support for OS X right click Väinö Järvelä
2007-08-04 6:55 ` Shawn O. Pearce
2007-08-04 7:11 ` Jeff King
2007-08-04 7:33 ` Shawn O. Pearce
2007-08-04 7:41 ` Jeff King
2007-08-05 2:48 ` Shawn O. Pearce
2007-08-04 16:37 ` Linus Torvalds [this message]
2007-08-04 17:49 ` Jeff King
2007-08-04 17:58 ` Jeff King
2007-08-04 11:36 ` Väinö Järvelä
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.0.999.0708040928350.5037@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
--cc=v@pp.inet.fi \
/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).