Petr Baudis <[EMAIL PROTECTED]> writes:
> Note that I really _loved_ the Daniel's tools while they lasted. What I
> loved most about them was that they really only pulled objects I needed
> and not a single worthless one. Does the current HTTP transport share
> this property?
I am a big fan of Barkalow puller, too. It is conceptually
simple, very easy to explain, and quite nicely done to be
transport independent. Performance sucks, but that is not Dan's
If we are talking about a dumb HTTP server that has packed and
then prune-packed its repository, "not a single worthless one"
is asking for moon. If Jeff packed all his 50 branches into a
single pack and prune packed his repository, the only thing a
dumb server could do when you ask for one of his branches is to
give you that statically prepared single pack which contains
everything, because there would be nothing in .git/objects/??/.
You need some CGI support that pulls only needed objects out of
that pack and talks a moral equivalent of the upload-pack
protocol for that.
Barkalow puller is still useful when all the objects you still
need to pull from the remote are unpacked on the remote end.
That's how I resurrected "git clone" over http with packed dumb
servers. For "clone" case, I just slurp all the available
packs, and have Barkalow puller take over the rest.
I have an early WIP for "git fetch", but I have backburnered it
for quite some time. I'll push it in its current form into my
proposed updates branch, so interested people can hack on it.
> Note that I also want to setup a simple "proof-of-concept" GIT homepage
> tomorrow. Well, write it, where it should be hosted can be worked out
> later and I have places for it to reside at for now. (Suggestions for
> final hosting welcome. In reality, how nice (and persistent) the URL
> gets is probably the only thing that really matters. My attempt will
> live at http://git.or.cz/.)
I hope nobody starts another SCM project called CZ ;-).
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