Elijah Newren

There is no scheme tailored to do this currently. You can specify --path (perhaps together with --invert-paths) to pick paths to keep or remove, which would remove the actual commits...

I'm glad you are enjoying the script. setup.py exists solely for uploading git-filter-repo to PyPI, which only someone doing releases should run. Someone else contributed it (and I have to...

Let's take a step back for a second; because I suspect there's a better solution than repeatedly rewriting history here. In general, repositories can have hundreds of thousands of commits...

Ah, so not really version control; that lessens my worries considerably and the usecase does sound like it might make sense. For your case, I think it's basically a case...

When you rewrite the history to remove the old commits, it will change the commit hashes for all the newer commits. That means that if only one side rewrites history,...

Hi, I'm so sorry for being absent for so long. The changes are very interesting! Thanks for submitting this. A couple small notes: Commit messages should be wrapped at 72...

I'm not sure what you're asking for. The title to me sounds like you want a new git repository with the portion of history from the main repo that only...

Submodule splitting and rejoining is not trivial; if it were, I would have made an example program in contrib/filter-repo-demos/ showing it off. I did start on a project to do...

I'm not aware of any attempts or progress in this area, though people occasionally query about it and may have tried or might be trying to implement something. I'm not...

Yep, I should check the exit status and handle it; good catch. A couple other points: * Your filter-repo script is probably unnecessary; you could use the insert-beginning contrib script...