You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Help minimize export dumps differences when inspecting --dry-run results
When diffing the fast-export dumps produces by `--dry-run`, it appears
that git-filter-repo is using Python's default sorting algorithm for
Git filenames, rather than the fast-export-specific algorithm, which
is implemented at:
https://github.com/git/git/blob/14de3eb34435db79c6e7edc8082c302a26a8330a/builtin/fast-export.c#L444-L448
```
$ ./git-filter-repo --dry-run --proceed
$ diff -u .git/filter-repo/fast-export.original .git/filter-repo/fast-export.filtered
...
@@ -1451,25 +1329,23 @@
D testcases/expected/case1-twenty
D testcases/inputs/case1
M 100755 0a13abf testcases/t9390-repo-filter.sh
+M 100644 de3799f testcases/t9390/case1
M 100644 e0c8845 testcases/t9390/case1-filename
M 100644 a1aa78f testcases/t9390/case1-ten
M 100644 488cbd9 testcases/t9390/case1-twenty
-M 100644 de3799f testcases/t9390/case1
```
Note: this has no consequences on the resulting Git
repository. git-filter-repo doesn't write tree objects directly; it
has git-fast-import do that. git-fast-import states that the order of
the filemodify directives given to it does not matter. This change
only avoids distracting differences when inspecting the modified
fast-export stream.
Signed-off-by: Sylvain Beucler <[email protected]>
0 commit comments