git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mason <slash.tmp@free.fr>
To: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Cc: git <git@vger.kernel.org>
Subject: Re: Quoted-printable support in git am
Date: Thu, 5 Oct 2017 13:58:57 +0200	[thread overview]
Message-ID: <683bd77f-ecf2-33e9-8f45-24545a2785eb@free.fr> (raw)
In-Reply-To: <CAPc5daX+N_Z6v-NxOb5cHh1V3Ctu7uQ+QFHzN9ATTQ22pVAfQw@mail.gmail.com>

On 05/10/2017 11:43, Junio C Hamano wrote:

> On Thu, Oct 5, 2017 at 6:30 PM, Jeff King wrote:
> 
>> Mason wrote:
>>
>>> The patch header contains:
>>>
>>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>> Content-Transfer-Encoding: quoted-printable
>>
>> That looks right. Though I wouldn't be surprised if whatever generated
>> the "flowed" also screwed up patch whitespace.
>> ...
>> If it does have the qp bits decoded, then I'd suspect that maybe there's
>> whitespace damage caused by the MUA.
> 
> I would be surprised if MUA that says format=flawed did _not_ mangle the patch.

format=flawed  :-) Did you write that on purpose?

Anyway, it turns out that I had somehow managed to generate an invalid patch
(with a spurious leading space in the 3+3 context lines); the quoted-printable
mangling was, in fact, a red-herring. Doh!

Sorry for the noise.

      reply	other threads:[~2017-10-05 11:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05  9:15 Quoted-printable support in git am Mason
2017-10-05  9:30 ` Jeff King
2017-10-05  9:43   ` Junio C Hamano
2017-10-05 11:58     ` Mason [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=683bd77f-ecf2-33e9-8f45-24545a2785eb@free.fr \
    --to=slash.tmp@free.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).