From: Andy Whitcroft <apw@shadowen.org>
To: Andreas Ericsson <ae@op5.se>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git.kernel.org not putting out or git-daemon bug?
Date: Wed, 06 Sep 2006 14:11:29 +0100 [thread overview]
Message-ID: <44FEC901.4070509@shadowen.org> (raw)
In-Reply-To: <44FEC6BE.5060301@op5.se>
Andreas Ericsson wrote:
> Is it just me, or is anyone else having problems 'git fetch'-ing from
> git.kernel.org? I've been trying on and off for two hours now, but keep
> getting
>
> fatal: unexpected EOF
> Fetch failure: git://git.kernel.org/pub/scm/git/git.git
>
> Around 10 o'clock GMT I got a couple of timeouts, but I haven't seen one
> of those for several hours now.
>
> Using git version 1.4.2.ga444 to do the fetching, and trying to pull
> things on to a clone of that revision of the git repo.
I am seeing the same. I switched my URL: to http and that got me the
data, so its still out there.
-apw
next prev parent reply other threads:[~2006-09-06 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 13:01 git.kernel.org not putting out or git-daemon bug? Andreas Ericsson
2006-09-06 13:11 ` Andy Whitcroft [this message]
2006-09-06 13:15 ` Andreas Ericsson
2006-09-06 18:17 ` Marco Costalba
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=44FEC901.4070509@shadowen.org \
--to=apw@shadowen.org \
--cc=ae@op5.se \
--cc=git@vger.kernel.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).