Hi Christian, Thanks for your reply. 2014-10-30 19:54 GMT+03:00 Christian Couder <christian.couder@xxxxxxxxx>: > On Thu, Oct 30, 2014 at 4:39 PM, Dmitry Oksenchuk <oksenchuk89@xxxxxxxxx> wrote: >> We're in the middle of conversion of a large CVS repository (20 years, >> 70K commits, 1K branches, 10K tags) to Git and considering two >> separate Git repositories: "historical" with CVS history and "working" >> created without history from heads of active branches (10 active >> branches). This allows us to have small fast "working" repository for >> developers who don't want to have full history locally and ability to >> rewrite history in "historical" repository (for example, to add >> parents to merge commits or to fix conversion mistakes) without >> affecting commit hashes in "working" repository (the hashes can be >> stored in bug tracker or in the code). > > This might be a good idea. Did you already test that the small > repository is really faster than the full repository? Yes, because of such amount of refs, push in "historical" repository takes 12 sec, push in "working" repository takes 0.4 sec, push in "joined" repository takes 2 sec. Local operations with history like log and blame work with the same speed in "joined" repository as in "historical" repository. >> Are there any disadvantages of using grafts and replace? Will both of >> them be supported in future versions of Git? > > My opinion is that grafts have no advantage compared to replace refs. > > Once you have created your replace refs, they can be managed like > other git refs, so they are easier to distribute. > > Basically if you want to get the full history on a computer you just need to do: > > git fetch 'refs/replace/*:refs/replace/*' That's true but you still need to have another remote with full history because it has lots of tags and branches that will be cloned by initial clone. Regards, Dmitry -- 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