Re: Handling large files with GIT
- From
Linus Torvalds <torvalds@osdl.org>
- Date
- Feb 13, 2006, 03:42 UTC
- Message-ID
- <Pine.LNX.4.64.0602121939070.3691@g5.osdl.org>
- In-Reply-To
- <Pine.OSX.4.64.0602131416530.25089@piva.hawaga.org.uk>
On Mon, 13 Feb 2006, Ben Clifford wrote:
Show 11 quoted lines
> > I've been keeping maildir in git for a few months, with mail being delivered > into a git repo on one (permanently connected) host and me merging that branch > into a repo on my laptop for reading (the intention being that I should be > able to sync it back to the permanently connected host as I sometimes read > mail there. > > Alas, the merge part of this absolutely sucks -- as time goes by, its getting > slower and slower (its taking an hour or so to do the merge, which has got to > the point of being barely usable -- if it wasn't for the neat hack-value, I'd > have given up on this by now).
If it takes an hour per merge, it _is_ unusable. I consider 15 _seconds_ to be pretty unusable.
Can you do a
git-ls-tree -r -t HEAD git-ls-tree -r -t HEAD^1 git-ls-tree -r -t HEAD^2
after a merge, and put the three resulting files up somewhere public (I assume the filenames aren't going to be anything private, I don't know how maildir organizes stuff) so that people can get an idea of what ends up being involved there..
Linus