From: Nick Hengeveld <nickh@reactrix.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <junkio@cox.net>,
"Randal L. Schwartz" <merlyn@stonehenge.com>,
git@vger.kernel.org
Subject: Re: maybe breakage with latest git-pull and http protocol
Date: Sat, 15 Oct 2005 14:56:48 -0700 [thread overview]
Message-ID: <20051015215648.GC5509@reactrix.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0510151502290.23242@iabervon.org>
On Sat, Oct 15, 2005 at 03:41:35PM -0400, Daniel Barkalow wrote:
> > BTW, I do not think this is related to git.git repository
> > problem, but I wonder why we do not do fetch_object() against
> > each altbase in http-fetch.c::fetch(); nobody said you cannot
> > borrow unpacked object from your neighbour.
>
> I believe the code is doing that, but elsewhere.
Er, never mind what I said in my previous message. Daniel is correct,
process_curl_messages() will try the next altbase if a request 404s.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next prev parent reply other threads:[~2005-10-15 21:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 0:53 maybe breakage with latest git-pull and http protocol Randal L. Schwartz
2005-10-13 5:50 ` Junio C Hamano
2005-10-14 10:58 ` Randal L. Schwartz
2005-10-14 15:42 ` Junio C Hamano
2005-10-14 16:18 ` Randal L. Schwartz
2005-10-14 19:56 ` Daniel Barkalow
2005-10-15 13:03 ` Randal L. Schwartz
2005-10-15 16:04 ` Junio C Hamano
2005-10-15 16:22 ` Junio C Hamano
2005-10-15 19:41 ` Daniel Barkalow
2005-10-15 21:56 ` Nick Hengeveld [this message]
2005-10-15 21:21 ` Nick Hengeveld
2005-10-15 16:37 ` Junio C Hamano
2005-10-15 17:13 ` Junio C Hamano
2005-10-15 21:57 ` Nick Hengeveld
2005-10-15 22:04 ` Randal L. Schwartz
2005-10-20 17:43 ` Nick Hengeveld
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=20051015215648.GC5509@reactrix.com \
--to=nickh@reactrix.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=merlyn@stonehenge.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.