Re: Initial push of a fully packed repo - why repack?

On Tue, 17 Apr 2007, Martin Langhoff wrote:

Pushing to a new empty repo, git spends a lot of time repacking, even
if we have just run git-repack. The process looks like

- use parsecvs to import a large CVS repo
- git-repack -a -d (packs to ~550MB, taking ~1hr)
- git-push --all git+ssh://host/newlycreatedrepo.git

Does it make sense to detect and optimise for this case?

Maybe...  Although the second repack during the push should be much much 
faster than the first one.


Nicolas