From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git pull cannot find remote refs.
Date: Tue, 28 Feb 2006 17:19:29 +0100 [thread overview]
Message-ID: <20060228161928.GA4829@scotty.home> (raw)
In-Reply-To: <7vlkvwuvyl.fsf@assigned-by-dhcp.cox.net>
Also sprach Junio C Hamano am Mon, 27 Feb 2006 at 17:13:22 -0800:
> ls-remote shows "SHA1\tPATH". The original says "hexadecimal
> followed by [either a single space or a single tab] followed by
> difference. Puzzled...
Grmph... You are right.
> I've seen two servers DNS round-robin and one of them fail to
> respond. The first "fetch" goes to the good one and the second
> ls-remote goes to the bad one, then you would see "Oops, we
> cannot peek tags". But this patch does not have anything to do
> with that problem..
Trapped. I haven't seen this, but perhaps it was the problem.
I'll watching for the next occurence.
Sorry for the noise.
Stefan
--
Stefan-W. Hahn It is easy to make things.
/ mailto:stefan.hahn@s-hahn.de / It is hard to make things simple.
prev parent reply other threads:[~2006-02-28 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 21:49 [PATCH] git pull cannot find remote refs Stefan-W. Hahn
2006-02-28 1:13 ` Junio C Hamano
2006-02-28 16:19 ` Stefan-W. Hahn [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=20060228161928.GA4829@scotty.home \
--to=stefan.hahn@s-hahn.de \
--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).