From: Todd Zullinger <tmz@pobox.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: git@vger.kernel.org
Subject: Re: git-am doesn't strip CRLF line endings when the mbox is base64-encoded
Date: Wed, 18 Dec 2019 14:41:44 -0500 [thread overview]
Message-ID: <20191218194144.GL17681@pobox.com> (raw)
In-Reply-To: <dece7350-7b58-bf19-9fdf-4ccf8df268fb@citrix.com>
George Dunlap wrote:
> On 12/18/19 11:42 AM, George Dunlap wrote:
>> Using git 2.24.0 from Debian testing.
>>
>> It seems that git-am will strip CRLF endings from mails before applying
>> patches when the mail isn't encoded in any way. It will also decode
>> base64-encoded mails. But it won't strip CRLF endings from
>> base64-encoded mails.
>>
>> Attached are two mbox files for two different recent series.
>> plainenc.am applies cleanly with `git am`, while base64enc.am doesn't.
>>
>> Poking around the man pages, it looks like part of the issue might be
>> that the CRLF stripping is done in `git mailsplit`, before the base64
>> encoding, rather than after.
>
> Poking around -- it looks like the CRLF stripping would be better done
> in `git mailinfo` after the decoding.
>
> Also, this can *almost* be worked around using hooks -- there's an
> `applypatch-msg` hook which can strip the CLRFs from the commit message,
> but no hook (AFAICT) corresponding `applypatch-patch` which is run on
> the patch itself before being applied.
This came up recently in <20191130180301.5c39d8a4@lwn.net>¹.
I don't know if any of that discussion will prove useful to
you if you want to poke at this further or not.
¹ https://lore.kernel.org/git/20191130180301.5c39d8a4@lwn.net/
--
Todd
next prev parent reply other threads:[~2019-12-18 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 11:42 git-am doesn't strip CRLF line endings when the mbox is base64-encoded George Dunlap
2019-12-18 12:15 ` George Dunlap
2019-12-18 19:41 ` Todd Zullinger [this message]
2020-01-06 11:58 ` George Dunlap
2020-01-06 17:07 ` Junio C Hamano
2020-01-06 18:10 ` George Dunlap
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=20191218194144.GL17681@pobox.com \
--to=tmz@pobox.com \
--cc=george.dunlap@citrix.com \
--cc=git@vger.kernel.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).