Petr Baudis wrote: > Dear diary, on Fri, Sep 08, 2006 at 05:50:40PM CEST, I got a letter > where Jakub Narebski <jnareb@xxxxxxxxx> 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 - 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