Hi everyone,
git-filter-repo[1], a filter-branch-like tool for rewriting repository
history, is ready for more widespread testing and feedback. The rough
edges I previously mentioned have been fixed, and it has several useful
features already, though more development work is ongoing (docs are a
bit sparse right now, though -h provides some help).
Why filter-repo vs. filter-branch?
* filter-branch is extremely to unusably slow (multiple orders of
magnitude slower than it should be) for non-trivial repositories.
* filter-branch made a number of usability choices that are okay for
small repos, but these choices sometimes conflict as more options
are combined, and the overall usability often causes difficulties
for users trying to work with intermediate or larger repos.
* filter-branch is missing some basic features.
The first two are intrinsic to filter-branch's design at this point
and cannot be backward-compatibly fixed.
Requirements:
* Python 2 (for now?)
* A version of git with en/fast-export-import topic (in master of git.git)
* A version of git with the --combined-all-names option to diff-tree;
I have submitted[2] this patch, but it hasn't been picked up yet.
What's the future? (Core command of git.git? place it in contrib? keep it
in a separate repo?) I'm hoping to discuss that at the contributor summit
today, but feedback on the list is also welcome.
Thanks,
Elijah
[1] https://github.com/newren/git-filter-repo; it's a ~2800 line
single-file python script, depending only on the python standard
library (and execution of git commands), all of which is designed
to make build/installation trivial: you just need to add it to
your $PATH.
[2] https://public-inbox.org/git/20190126221811.20241-1-newren@xxxxxxxxx/
