From: ebiederm@xmission.com (Eric W. Biederman)
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Last mile to 1.0?
Date: Sat, 16 Jul 2005 12:36:43 -0600 [thread overview]
Message-ID: <m18y06pphg.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <7vwtnqhcfb.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Sat, 16 Jul 2005 10:46:00 -0700")
Junio C Hamano <junkio@cox.net> 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
next prev parent reply other threads:[~2005-07-16 18:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 17:46 Last mile to 1.0? Junio C Hamano
2005-07-16 18:36 ` Eric W. Biederman [this message]
2005-07-17 0:49 ` Junio C Hamano
2005-07-17 1:18 ` David Lang
2005-07-18 5:44 ` Junio C Hamano
2005-07-18 4:53 ` Alexey Nezhdanov
2005-07-18 5:35 ` Junio C Hamano
2005-07-18 6:48 ` Alexey Nezhdanov
2005-07-18 7:38 ` Junio C Hamano
2005-07-23 8:15 ` Ryan Anderson
2005-07-23 12:56 ` Gene Heskett
2005-07-24 0:53 ` [PATCH 0/6] A bit better dumb server support Junio C Hamano
2005-07-23 8:50 ` Last mile to 1.0? Ryan Anderson
2005-07-23 13:14 ` Gene Heskett
2005-07-23 14:47 ` Kevin Smith
2005-07-23 17:09 ` Junio C Hamano
2005-07-24 3:12 ` Alexey Nezhdanov
2005-07-29 22:41 ` Petr Baudis
2005-07-30 2:11 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-07-30 5:40 barkalow
2005-07-30 8:07 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m18y06pphg.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).