From: Junio C Hamano <junkio@cox.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, kha@treskal.com, bfields@fieldses.org
Subject: Re: testing vger handling of charsets (part 2)
Date: Tue, 15 May 2007 23:34:02 -0700 [thread overview]
Message-ID: <7vmz05ffad.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070515test.2@coredump.intra.peff.net> (Jeff King's message of "Tue, 15 May 2007 03:13:40 -0400")
Jeff King <peff@peff.net> writes:
> This is a test message to check how vger reacts to seeing 8bit
> characters (like Hasselström) in a message _with_ the right mime
> header.
>
> If your mail server doesn't advertise the 8BITMIME extensions, I expect
> this message to come through OK, since vger will (hopefully) respect the
> existing content-type header. Karl and Bruce, can you please report?
I think you are trying to figure out how vger adds/munges the
headers, and the above is not very useful for people but
yourself unless you explicitly say what headers you gave on your
end in the body of the message, is it?
Judging from the list responses, I am guessing the situation is
like this. Does that match your understanding?
botched one:
outgoing:
body in utf-8
Content-type: text/plain; charset=utf-8
no MIME-Version: header
vger relayed to recipients:
body untouched
Content-type: text/plain; charset=iso-8859-1
MIME-Version: 1.0
good one:
outgoing:
body in utf-8
Content-type: text/plain; charset=utf-8
MIME-Version: 1.0
vger relayed to recipients: everything intact.
I am not sure what exactly you meant by with/without "the right
mime header", but the above is based on my guess that you meant
only MIME-VERSION header.
next prev parent reply other threads:[~2007-05-16 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 7:13 testing vger handling of charsets (part 2) Jeff King
2007-05-15 8:31 ` Karl Hasselström
2007-05-15 14:59 ` J. Bruce Fields
2007-05-16 6:34 ` Junio C Hamano [this message]
2007-05-16 9:29 ` Jan Hudec
2007-05-16 10:57 ` Jeff King
2007-05-16 10:55 ` Jeff King
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=7vmz05ffad.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=peff@peff.net \
/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).