Re: Change set based shallow clone

From: Jakub Narebski <jnareb@gmail.com>
Date: Sep 9, 2006, 08:39 UTC
Message-ID: <edtuj5$p76$1@sea.gmane.org>
In-Reply-To: <20060909031307.GE23891@pasky.or.cz>

Petr Baudis wrote:

Show 14 quoted lines

> Dear diary, on Fri, Sep 08, 2006 at 05:50:40PM CEST, I got a letter
> where Jakub Narebski <jnareb@gmail.com> said that...
>> My idea for lazy clone/fetch (lazy = on-demand) is via remote alternatives
>> mechanism. We put URI for repository (repositories) that hosts the project,
>> and we would need at start to download at least heads and tags, and only
>> heads and tags.
> 
>   One thing to note is that you won't last very long without getting
> at least basically all the commits from the history. git log, git
> merge-base and such would either just suck them all, get partially moved
> to the server side, or would undergo quite a painful and slooooooooow
> process "get me commit X... thank you, sir. hmm, it appears that its
> parent is commit Y.  could you get me commit Y, please...? thank you,
> sir. hmm, it appears...".

As I said there is load of troubles with lazy clone/fetch = remote alternatives I didn't thought about.

git log/git rev-list and git fsck-objects among them.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git