git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>,
	git@vger.kernel.org, "Brian Swetland" <swetland@google.com>,
	"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	"Nicolas Pitre" <nico@cam.org>
Subject: Re: [BUG] encoding problem with format-patch + send-email
Date: Fri, 16 Nov 2007 16:48:37 -0800	[thread overview]
Message-ID: <7vlk8xwvbu.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071116104907.GA13087@sigill.intra.peff.net> (Jeff King's message of "Fri, 16 Nov 2007 05:49:09 -0500")

Jeff King <peff@peff.net> writes:

> git-send-email: add charset header if we add encoded 'From'

Thanks.

> If we already had a content-type header in the mail, then we
> may need to re-encode. The logic is there to detect
> this case, but it doesn't actually do the re-encoding.

Although the charset on rfc2047 encoded header fields can be
independent of the charset in the body, I think you need to do
crazy things to do so.

Will queue.

  parent reply	other threads:[~2007-11-17  0:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 10:57 [BUG] encoding problem with format-patch + send-email Uwe Kleine-König
2007-11-16 10:49 ` Jeff King
2007-11-16 11:14   ` Uwe Kleine-König
2007-11-17  0:48   ` Junio C Hamano [this message]
2007-11-19 10:49     ` Uwe Kleine-König
2007-11-19 10:58       ` Brian Swetland
2007-11-20 12:54       ` [PATCH] send-email: add transfer encoding header with content-type Jeff King
2007-11-20 13:49         ` Uwe Kleine-König
2007-11-21  6:58         ` Junio C Hamano

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=7vlk8xwvbu.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Uwe.Kleine-Koenig@digi.com \
    --cc=git@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nico@cam.org \
    --cc=peff@peff.net \
    --cc=swetland@google.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).