From: Russ Allbery <rra@debian.org>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Stefan-W. Hahn" <stefan.hahn@s-hahn.de>,
"Lukas Sandström" <luksan@gmail.com>, "Jeff King" <peff@peff.net>,
"Christian Himpel" <chressie@googlemail.com>
Subject: Re: Make format-patch produce UTF-8 `From:' header
Date: Sun, 19 Sep 2010 12:19:00 -0700 [thread overview]
Message-ID: <87mxrda6e3.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <87y6axshmt.fsf_-_@gmail.com> ("Štěpán Němec"'s message of "Sun, 19 Sep 2010 20:38:50 +0200")
Štěpán Němec <stepnem@gmail.com> writes:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>> Maybe format-patch could provide another mode to produce patches that
>> do not include unnecessary headers (in particular, leaving out the
>> difficult "From " line and using UTF-8 instead of quoted-printable for
>> the "From: " line).
> FWIW, the quoted-printable `From:' encoding has always annoyed me -- I
> replace it manually with my name & address in UTF-8 every time I send
> out a patch. What is the reason format-patch does that (and if there is
> a reason not to change the default, could an option to disable it be
> provided)?
Well, it's required if you're going to actually send the result directly
as a mail message, since the RFC 5322 format requires headers be encoded
using RFC 2047 encoding. But if you're just attaching the patch to
another mail message, it's pointless.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2010-09-19 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 14:24 git am should recognize >From Jonathan Nieder
2010-09-19 14:32 ` Jonathan Nieder
2010-09-19 18:01 ` Russ Allbery
2010-09-19 18:38 ` Make format-patch produce UTF-8 `From:' header (was Re: git am should recognize >From) Štěpán Němec
2010-09-19 19:19 ` Russ Allbery [this message]
2010-09-20 12:20 ` use base64 instead of quoted-printable in format-patch headers (was Re: Make format-patch produce UTF-8 `From:' header) Štěpán Němec
2010-09-20 13:46 ` Ævar Arnfjörð Bjarmason
2010-09-20 15:29 ` Brandon Casey
2010-09-20 15:55 ` use base64 instead of quoted-printable in format-patch headers Štěpán Němec
2010-09-19 19:44 ` Make format-patch produce UTF-8 `From:' header (was Re: git am should recognize >From) Erik Faye-Lund
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=87mxrda6e3.fsf@windlord.stanford.edu \
--to=rra@debian.org \
--cc=chressie@googlemail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=luksan@gmail.com \
--cc=peff@peff.net \
--cc=stefan.hahn@s-hahn.de \
--cc=stepnem@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.