Re: Trying to use git-filter-branch to compress history by removing large, obsolete binary files
- From
- J. Bruce Fields <bfields@fieldses.org>
- Date
- Oct 8, 2007, 01:00 UTC
- Message-ID
- <20071008010033.GA25654@fieldses.org>
- In-Reply-To
- <Pine.LNX.4.64.0710080129480.4174@racer.site>
On Mon, Oct 08, 2007 at 01:34:07AM +0100, Johannes Schindelin wrote:
> It does what it should do. It is _your_ task to look at refs/original/* > if everything went alright. Then you just delete the checked refs.
It seems odd to me, by the way, that filter-branch has its own home-grown backup mechanism. Lots of other commands can "lose" commits, but none of them keep an extra backup like this.
And I find it tedious for quicker jobs which it might otherwise be useful for (e.g. rewrites of commits in my tree not yet in upstream), unless I wrap it in a script that cleans up after itself.
--b.