Re: [QUESTION] Access to a huge GIT repository.
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Nov 16, 2005, 20:01 UTC
- Message-ID
- <46a038f90511161201h54c5fa73l20b5dcf3b5c19399@mail.gmail.com>
- In-Reply-To
- <7vveys8n8q.fsf@assigned-by-dhcp.cox.net>
On 11/17/05, Junio C Hamano <junkio@cox.net> wrote:
Show 5 quoted lines
> The underlying network transfer program, 'git-clone-pack', can > be told to clone only specified branches. If somebody is > interested, updating the 'git-clone' wrapper to use it should > not be too hard -- obviously this needs to be done for other > transports as well, though.
cg-clone already does this. One tricky thing with the selective cloning is that you want to pull the named head plus all its related objects, and then pull only the _relevant_ tags. There's been discussion of pulling tagsrefs+related tag objects and then pruning any tagrefs+tagobjects where the commit is unreachable with the objects you already have. You surely remember my 'git-rev-parse is crashing' thread.
If you just pull tagrefs and all the objects needed for them, chances are you'll get the whole repo anyway ;-)
cheers,
martin