From: Keith Owens <kaos@sgi.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Daniel Barkalow <barkalow@iabervon.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org, tony.luck@intel.com
Subject: Re: Current state of GIT fetch/pull clients
Date: Fri, 16 Sep 2005 15:49:11 +1000 [thread overview]
Message-ID: <8953.1126849751@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 15 Sep 2005 16:52:20 MST." <7vbr2tx51n.fsf@assigned-by-dhcp.cox.net>
On Thu, 15 Sep 2005 16:52:20 -0700,
Junio C Hamano <junkio@cox.net> wrote:
>What this means is that using objects/info/alternates mechanism
>in your repository is a bit premature as things currently stand,
>if you intend your repository to be used by the general public.
Clients using rsync can use a workaround, although it is a bit clumsy.
I do rsync for selected /pub/scm/linux/kernel/git/ trees, including
torvalds and aegl. At one point Tony Luck (aegl) was using alternates,
with objects/info/alternates containing
/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/objects
As you described in your mail, rsync with alternates overwrites the
local file, so the local alternates ended up pointing at a local
directory that did not exist. Creating a local symlink from
/pub/scm/linux/kernel/git to the local directory that contains the
torvalds and aegl directories worked around the problem. git checkout
on the aegl tree was quite happy to follow the symlink and pick up most
of the files from torvalds.
No point in doing that now, Tony has reverted the aegl tree to a full
copy of Linus, instead of using alternates.
prev parent reply other threads:[~2005-09-16 5:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 3:26 [PATCH RFC] Add support for alternates in HTTP Daniel Barkalow
2005-09-15 23:52 ` Current state of GIT fetch/pull clients Junio C Hamano
2005-09-16 1:03 ` Jeff Garzik
2005-09-16 5:49 ` Keith Owens [this message]
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=8953.1126849751@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@osdl.org \
/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).