On Sat, 9 Jul 2005, Eric W. Biederman wrote:
> I assume the problem with the mirror it model was simply there were
> to many objects?
> > And then you really can use just rsync or wget or ncftpget or anything
> > else that has a "fetch recursively, optimizing existing objects" mode.
> Sane. But with an intelligent fetcher and a little extra information a
> dumb server should still be able to not fetch branches we care nothing
> about. I think that extra information is simply commit object graph and
> which packs those commit objects are in. I assume the commit graph
> information will be fairly modest.
Well, what I'd hope for is actually that eventually "webgit" will have
some machine-parseable sub-tree, and then you can have this kind of thing
But a _truly_ dumb server (ie one with no CGI at all, just "raw data", you
really end up with just effectively rsyncing it. Yes, you could create a
new "commit index file" every time you push, and maybe it's worth it, but
on the other hand, what's wrong with just rsyncing it all and parsing it
People who use it for major development would all try to get the smart
client, even if it's "just" some webgit extension thing..
Dumb servers work, they just won't do any selective stuff. Big deal.
That's why they are dumb.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html