Initial push of a fully packed repo - why repack?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

cheers,


martin
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]