From: "Tony Luck" <tony.luck@gmail.com>
To: "Brian Gerst" <bgerst@didntduck.org>
Cc: "Linus Torvalds" <torvalds@osdl.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: fatal: unexpected EOF
Date: Tue, 28 Feb 2006 07:59:09 -0800 [thread overview]
Message-ID: <12c511ca0602280759t2e584a4bkd7b6f4d97ade92f7@mail.gmail.com> (raw)
In-Reply-To: <44046F94.3070806@didntduck.org>
> I doubt it is a problem with mirroring, since it affects all repos
> (kernel, git, cogito, etc.) at the same time.
Ditto. Jes has been grumbling overnight that he can't get a reliable pull
from my kernel repo ... and that hasn't been updated in 10 days, so the
mirror code shouldn't be touching it. His error was:
fatal: read error (Connection reset by peer)
Fetch failure: git://git.kernel.org/pub/...
He also reported that after a few retries it worked.
Does the git daemon log any errors to syslog on the server? If so, can someone
with access go take a look.
-Tony
next prev parent reply other threads:[~2006-02-28 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 13:02 fatal: unexpected EOF Brian Gerst
2006-02-28 15:34 ` Linus Torvalds
2006-02-28 15:43 ` Brian Gerst
2006-02-28 15:59 ` Tony Luck [this message]
2006-03-02 22:23 ` Alex Riesen
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=12c511ca0602280759t2e584a4bkd7b6f4d97ade92f7@mail.gmail.com \
--to=tony.luck@gmail.com \
--cc=bgerst@didntduck.org \
--cc=git@vger.kernel.org \
--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).