Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > FWIW if anybody cares about my opinion: I would be totally fine with > integrating git-filter-repo into git.git, have it there for a major > version or two, then patch `git filter-branch` to spew out a deprecation > warning, and then remove that latter command a major version (or two) > later. Yup, that's just the usual deprecate then delete sequence. The compatibility wrapper brought up in the discussion earlier would be a big plus ;-)
