Junio C Hamano <[EMAIL PROTECTED]> writes:

> I do not know what release plan Linus has in mind, and also
> expect things to be quieter next week during OLS and kernel
> summit, but I think we are getting really really close.
>
> Here are the things I think we would want to see before we hit
> 1.0:
>
>  - Remaining feature enhancements and fixes.
>
>    - Anonymous pull from packed archives on remote sites via
>      non-rsync, non-ssh transport.  Many people are behind
>      corporate firewalls that do not pass anything but outgoing
>      http(s) and some do not even pass outgoing ssh.  The recent
>      addition of git-daemon by Linus would greatly alleviate the
>      situation, but we may also end up wanting something HTTP
>      reachable.

For this we need a cgi script that will generate an appropriate
pack.  Although stupid http fetching may have some potential
if we ditch libcurl and use pipelining for http 1.1.  Bandwidth
wise that will never equal a custom pack because it will not do
deltas.  But in the common case of an incremental pull it should
be able to equal rsync.

Do we want to put some porcelain around, git-fsck-cache --tags?
So we can discover the tag objects in the archive and place
them someplace usable.  Jeff Garzik in his howto is still recommending:

>   git-pull-script only downloads sha1-indexed object data, and the requested 
> remote head.
>   This misses updates to the .git/refs/tags/ and .git/refs/heads/ 
> directories. It is
>   advisable to update your kernel .git directories periodically with a full 
> rsync command, to
>   make sure you got everything:
>$ cd linux-2.6
>$ rsync -a --verbose --stats --progress \
>   rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/ \
>   .git/

Which feels like something is missing.  Given that tags are
sha1-indexed objects we should be pulling them.  And I believe you can
have a tag as a parent of a commit, so even with the pack optimized
clients we should be pulling them now.  


Eric
-
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

Reply via email to