Re: Performance issue exposed by git-filter-branch
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Dec 17, 2010, 02:51 UTC
- Message-ID
- <m3lj4sll39.fsf@localhost.localdomain>
- In-Reply-To
- <9A686258-A504-4CBB-9993-048B45B5EE6A@irridia.com>
Please do not toppost.
Ken Brownfield <krb@irridia.com> writes:
Show 6 quoted lines
> I had considered this approach (and the one mentioned by Jonathan) > but there are no git tools to actually perform the filter I wanted > on the export in this form. I could (and will) parse fast-export > and make an attempt a filtering files/directories... my concern is > that I won't do it right, and will introduce subtle corruption. But > if there's no existing tool, I'll take a crack at it. :-)
You can try ESR's reposurgeon:
http://www.catb.org/~esr/reposurgeon/
It's limitation is that it loads structure of DAG of revisions (but not blobs i.e. contents of file) to memory. IIRC. It is not streaming, but "DOM" based, otherwise some commands would not work.
By the way, git-filter-branch documentation recomments to use index-filter with git-update-index instead of tree-filter with git-rm, and if tree-filter is needed, to use some fast filesystem, e.g. RAM one.
But probably you know all that.
-- Jakub Narebski Poland ShadeHawk on #git