From: xiaozhu <xiaozhu@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: a bug about format-patch of multibyte characters comment
Date: Sun, 13 Feb 2011 17:45:41 +0900 [thread overview]
Message-ID: <4D579A35.1000007@gmail.com> (raw)
In-Reply-To: <20110213083137.GB12112@sigill.intra.peff.net>
> Shouldn't we still be generating "one two three", encoding it via
> rfc2047 if necessary, and _then_ deciding if folding is required? Yes,
> individual lines in a multi-line subject are good candidates for
> folding, but don't we need to be checking for and folding long lines
> anyway?
It seems that by rfc2047 there is no multi-line subject spec. A subject
with multi-line will be always conflated to one single line. And also
that if we just generate the subject within multi-line just like the
current implemention, yes, we can modify the git-am to decode it correctly,
but most of the mail client will can not show it correctly.
So it seems that there is only one way that combining the whole first
paragraph to a single line? But it will be a nightmare for some long comment.
next prev parent reply other threads:[~2011-02-13 8:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 10:13 a bug about format-patch of multibyte characters comment xiaozhu
2011-02-12 12:30 ` "Martin Krüger"
2011-02-13 7:53 ` Jeff King
2011-02-13 8:31 ` Jeff King
2011-02-13 8:45 ` xiaozhu [this message]
2011-02-13 8:52 ` Jeff King
2011-02-13 10:14 ` xiaozhu
2011-02-13 10:22 ` xzer
2011-02-13 10:26 ` Jeff King
2011-02-13 10:50 ` xiaozhu
2011-02-13 10:23 ` Jeff King
2011-02-13 9:48 ` Johannes Sixt
2011-02-13 10:03 ` 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=4D579A35.1000007@gmail.com \
--to=xiaozhu@gmail.com \
--cc=git@vger.kernel.org \
--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).