From: Johannes Schindelin Date: Mon, 08 Oct 2007 01:06:21 GMT Subject: Re: Trying to use git-filter-branch to compress history by removing large, obsolete binary files Message-ID: In-Reply-To: <20071008010033.GA25654@fieldses.org> Hi, On Sun, 7 Oct 2007, J. Bruce Fields wrote: > 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. The rationale was this: filter-branch recently learnt how to rewrite many branches, and it might be tedious to find out which ones. But then, there is git log --no-walk --all, so maybe I really should get rid of refs/original/*? I'd like to have some comments from the heavier filter-branch users on that... Ciao, Dscho