filter-repo: delete complex code
Over a decade ago, I added code to deal with splitting and splicing repositories where you weren't always dealing with first parents and linear histories, and in particular where the mainline tended to be the second parent (because there was no integrator or special central gatekeeper like gerrit or github; instead, everyone pushed directly to the main repository after locally testing, and integration happened via everyone running 'git pull'). When attempting to splice repositories the fact that fast-export always gave changes relative to the first parent caused some grief with my splitting and splicing efforts. It has been over a decade, I don't know of a good testcase of this functionality separate from the live repositories I lost access to over six years ago, git-subtree was released in the meantime which I'm certain handled the task better, git-fast-export since gained a --full-tree option which might have provided a better way to attack the problem (though with splicing repos you often want work with additive changes rather than recreating from scratch), and I just don't quite understand the code anymore anyway. I think it had some fundamental limitations that I knew my usecase avoided, but I don't remember the details (and I'm not certain if this is true). Even though code coverage hits all but one of the lines, I'd rather rewrite any needed functionality if the usecase arises, and in view of what facilities exist today rather than what I was working with a decade ago. So, just nuke this code. Signed-off-by: Elijah Newren <newren@gmail.com>pull/13/head
parent
cb9e3dd92c
commit
a31a381fb8
Loading…
Reference in New Issue