From: "Raymond E. Pasco" <ray@ameretat.dev>
To: git@vger.kernel.org
Cc: ray@ameretat.dev
Subject: [WIP PATCH] fast-export: emit deletions first
Date: Mon, 6 Apr 2026 02:36:03 -0400 [thread overview]
Message-ID: <20260406063607.15353-1-ray@ameretat.dev> (raw)
fast-export chooses its output order by pathname, sorting longer
paths earlier. However, this causes faulty output when the deleted
path is a prefix of the added one. For example, deleting a file 'a' and
creating a file 'a/b' emits:
from :prev_label
M 100644 :blob_label a/b
D a
Fix this by sorting deletions to come before other types of change.
Signed-off-by: Raymond E. Pasco <ray@ameretat.dev>
---
This is a quick and dirty fix for the bug. However, I do want to spend a
little more time on it - it may be that we only want to reverse the sort
when the deletion is specifically the prefix of some addition, and I
want to fence this off with new tests.
builtin/fast-export.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/builtin/fast-export.c b/builtin/fast-export.c
index b90da5e616..82d73b2f43 100644
--- a/builtin/fast-export.c
+++ b/builtin/fast-export.c
@@ -354,6 +354,12 @@ static int depth_first(const void *a_, const void *b_)
int len_a, len_b, len;
int cmp;
+ /* emit deletions first */
+ int a_deletes = (a->status == DIFF_STATUS_DELETED);
+ int b_deletes = (b->status == DIFF_STATUS_DELETED);
+ if (a_deletes != b_deletes)
+ return b_deletes - a_deletes;
+
name_a = a->one ? a->one->path : a->two->path;
name_b = b->one ? b->one->path : b->two->path;
--
2.54.0.rc0.605.g598a273b03.dirty
next reply other threads:[~2026-04-06 6:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 6:36 Raymond E. Pasco [this message]
2026-04-06 17:15 ` [WIP PATCH] fast-export: emit deletions first Junio C Hamano
2026-04-06 21:29 ` Jeff King
2026-04-06 21:44 ` Elijah Newren
2026-04-07 4:24 ` Jeff King
2026-04-07 21:28 ` Raymond E. Pasco
2026-04-07 1:12 ` Raymond E. Pasco
2026-04-07 4:26 ` 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=20260406063607.15353-1-ray@ameretat.dev \
--to=ray@ameretat.dev \
--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