From: Jeff King <peff@peff.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
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 13:58:26 -0400 [thread overview]
Message-ID: <20070804175826.GC17113@sigill.intra.peff.net> (raw)
In-Reply-To: <alpine.LFD.0.999.0708040928350.5037@woody.linux-foundation.org>
On Sat, Aug 04, 2007 at 09:37:17AM -0700, Linus Torvalds wrote:
> 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.
Well, that _is_ what the standard says, I believe. I agree with you that
practice is more important than a standard, and if there are high-bit
characters in the 'From' field, I think that using the body charset is a
reasonable guess (although keep in mind that the "body" could be hidden
below a multipart/mixed, multipart/alternative, or some other arcane
structure).
But I really have no idea why fully mime-aware mailers refuse to use
rfc2047 encoding of the headers. In fact, my copy of the message you
sent (to which I am replying) has munged Väinö's name in the cc header,
because it failed to use rfc2047 encoding. I'm surprised that alpine
would fail to get that right.
-Peff
next prev parent reply other threads:[~2007-08-04 17:58 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
2007-08-04 17:49 ` Jeff King
2007-08-04 17:58 ` Jeff King [this message]
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=20070804175826.GC17113@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=torvalds@linux-foundation.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).