From: Jonathan Nieder <jrnieder@gmail.com>
To: Peter Krefting <peter@softwolves.pp.se>
Cc: "Øyvind A. Holm" <sunny@sunbase.org>, git@vger.kernel.org
Subject: Re: MIME problem when using git format-patch / git am
Date: Tue, 27 Apr 2010 10:32:50 -0500 [thread overview]
Message-ID: <20100427153250.GA14756@progeny.tock> (raw)
In-Reply-To: <alpine.DEB.2.00.1004260948070.22806@ds9.cixit.se>
Peter Krefting wrote:
> Jonathan Nieder:
>> This leads to a question: what if one wants to include a word that
>> quotes to more than 75 characters?
>
> You just split it into two encoded words. The whitespace between the
> encoded words is there for syntactic reasons only, it is not
> included in the final result if both parts are encoded words (look
> at the "Examples" section of the RFC for some examples of how it
> works).
Thank you. He explains it before then, too; I should be reading more
carefully.
I’ve been working through a full implementation of that RFC, but it
seems that to support breaking words, Git would need to learn where the
character boundaries are. Which means encodings would not be just opaque
strings as far as git cares any more.
On the bright side, the only encoding I care about is UTF-8, and that
one’s easy.
Jonathan
prev parent reply other threads:[~2010-04-27 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 23:35 MIME problem when using git format-patch / git am Øyvind A. Holm
2010-04-26 1:49 ` Jonathan Nieder
2010-04-26 8:50 ` Peter Krefting
2010-04-27 15:32 ` Jonathan Nieder [this message]
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=20100427153250.GA14756@progeny.tock \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=peter@softwolves.pp.se \
--cc=sunny@sunbase.org \
/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).