I have a commit which looks like this:
$ git cat-file commit 4ca76eb7b47724c2444dfea7890fa8db4edd5762
tree c845be47a0653624b1984d0dc1a0b485b527811d
parent 9eee98638ef06149e17f94afaa357e3a9e296e69
author Florian Weimer [off-list ref] 1507481682 +0200
committer Florian Weimer [off-list ref] 1507481682 +0200
19: glibc-fedora-nis-rh188246.patch
From baba5d9461d4e8a581ac26fe4412ad783ffc73e7 Mon Sep 17 00:00:00 2001
From: Jakub Jelinek <redacted>
Date: Mon, 1 May 2006 08:02:53 +0000
Subject: [PATCH] Enable SETENT_BATCH_READ nis/nss option by default
* Mon May 1 2006 Jakub Jelinek [off-list ref] 2.4.90-4
- SETENT_BATCH_READ /etc/default/nss option for speeding up
some usages of NIS+ (#188246)
This commit causes git rebase to fail, with this error:
fatal: could not parse .git/rebase-apply/0008
At this point, .git/rebase-apply/0008 contains this:
“
From baba5d9461d4e8a581ac26fe4412ad783ffc73e7 Mon Sep 17 00:00:00 2001
From: Jakub Jelinek <redacted>
Date: Mon, 1 May 2006 08:02:53 +0000
Subject: [PATCH] Enable SETENT_BATCH_READ nis/nss option by default
* Mon May 1 2006 Jakub Jelinek [off-list ref] 2.4.90-4
- SETENT_BATCH_READ /etc/default/nss option for speeding up
some usages of NIS+ (#188246)
---
nis/nss | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/nis/nss b/nis/nss
index
0ac6774a1ff29f012efaec9c4be1fcc3b83da7e8..d720e719267db5f741b67e7b98e4052e503c4333
100644
”
Followed by the diff. The preceding patch, .git/rebase-apply/0007, is:
“
[fweimer@oldenburg glibc-patches]$ cat .git/rebase-apply/0007
From 4ca76eb7b47724c2444dfea7890fa8db4edd5762 Mon Sep 17 00:00:00 2001
From: Florian Weimer <redacted>
Date: Sun, 8 Oct 2017 18:54:42 +0200
Subject: 19: glibc-fedora-nis-rh188246.patch
”
Based on strace output, something in git rebase calls git mailsplit, and
it probably sees the "\nFrom " string and treats it as a start of a new
mail message, and things go downhill from there.
I will escape "\nFrom " in commit messages (probably as "\n.From " or
maybe "\n>From ", plus escaping for "\n."/"\n>" to make the encoding
reversible), but I wonder if there is something else I need to escape
while I'm at it.
Thanks,
Florian
From: Eric Wong <hidden> Date: 2017-10-08 21:31:10
Florian Weimer [off-list ref] wrote:
Based on strace output, something in git rebase calls git mailsplit, and it
probably sees the "\nFrom " string and treats it as a start of a new mail
message, and things go downhill from there.
I will escape "\nFrom " in commit messages (probably as "\n.From " or maybe
"\n>From ", plus escaping for "\n."/"\n>" to make the encoding reversible),
but I wonder if there is something else I need to escape while I'm at it.
I suppose it's safe to start using mboxrd internally when
there's little danger of mixing different git versions.
Totally untested (but passes "make test"), can you try this?
-----8<------
Subject: [PATCH] rebase: use mboxrd format to avoid split errors
The mboxrd format allows the use of embedded "From " lines in
commit messages without being misinterpreted by mailsplit
Reported-by: Florian Weimer <redacted>
Signed-off-by: Eric Wong <redacted>
---
git-rebase--am.sh | 2 ++
1 file changed, 2 insertions(+)
My context is slightly different, but I added the mboxrd options
manually to both commands, and it fixes my test case.
I'm still wondering if I have to be on the lookout for similar issues
with different strings.
Thanks,
Florian
My context is slightly different, but I added the mboxrd options manually to
both commands, and it fixes my test case.
I'm still wondering if I have to be on the lookout for similar issues with
different strings.
I don't think theres other issues with different strings,
"From " lines are the one known ambiguity problem with mbox and
thus the reason mboxrd was created.
Below is an updated patch which adds a test case:
---------8<---------
Subject: [PATCH] rebase: use mboxrd format to avoid split errors
The mboxrd format allows the use of embedded "From " lines in
commit messages without being misinterpreted by mailsplit
Reported-by: Florian Weimer <redacted>
Signed-off-by: Eric Wong <redacted>
---
git-rebase--am.sh | 2 ++
t/t3400-rebase.sh | 22 ++++++++++++++++++++++
2 files changed, 24 insertions(+)
@@ -255,4 +255,26 @@ test_expect_success 'rebase commit with an ancient timestamp' 'grep"author .* 34567 +0600$"actual'+test_expect_success'rebase with "From " line in commit message''+gitcheckout-bpreserve-frommaster~1&&+cat>From_.msg<<EOF&&+Somebodyembeddedanmboxinacommitmessage++Thisisfromso-and-so:++Froma@bMonSep1700:00:002001+From:JohnDoe<nobody@example.com>+Date:Sat,11Nov201700:00:00+0000+Subject:notthismessage++something+EOF+>From_&&+gitaddFrom_&&+gitcommit-FFrom_.msg&&+gitrebasemaster&&+gitlog-1--pretty=format:%B>out&&+test_cmpFrom_.msgout+'+ test_done