Re: RFC: Proposing git-filter-repo for inclusion in git.git
- From
- Eric Wong <e@80x24.org>
- Date
- Aug 23, 2019, 03:00 UTC
- Message-ID
- <20190823030059.47ftwfne6y436e5j@dcvr>
- In-Reply-To
- <CABPp-BFK65qL4GCs5bFuiPPYwMCDYrxMyYejacVS89d2GK4nDQ@mail.gmail.com>
Elijah Newren <newren@gmail.com> wrote:
Show 11 quoted lines
> * Remove git-filter-branch from git.git. Mention in the release > notes where people can go to get it.[1] > > filter-branch is not merely a slow or difficult-to-use tool, it's one > that *fosters* mistakes by making it hard to get things right in > several different ways. Granted, people exercise extra caution using > filter-branch because they know they need to, but there are so many > gotchas that they're likely to accidentally mess something up. Those > mess-ups are not always discovered immediately, and by then it's > nearly cast into stone (rewriting being something you want to do very > rarely).
Is it possible to turn git-filter-branch into a fast, compatible, and (maybe) safe wrapper for git-filter-repo? That would "fix" filter-branch and (if done carefully) not break existing uses.
It could also spew warnings to recommend safer switches.
Stability is a major reason I use git, the Linux kernel, and why I distrust+avoid desktop/GUI software. Removing "unsafe" features, even with good intentions, inevitably leads to frustrated users.