From: Tim O'Callaghan <timo@dspsrv.com>
To: git@vger.kernel.org
Subject: Re: unexpected EOF?
Date: Thu, 1 Dec 2005 14:49:17 +0100 [thread overview]
Message-ID: <20051201134917.GH2188@ELSAMSW37164> (raw)
In-Reply-To: <E1EhohG-0001iZ-IB@jdl.com>
On Thu, Dec 01, 2005 at 07:42:02AM -0600, Jon Loeliger wrote:
>
> I thought I had imagined this last time, but now
> that it has happened twice, I'm not so sure what
> is going on. First pull attempt garners an
> unexpected EOF message; immediately pull again
> seems to work.
>
> Some state:
>
> jdl@ubuntu:/usr/src/git-core$ git --version
> git version 0.99.9j
>
> jdl@ubuntu:/usr/src/git-core$ cat .git/remotes/origin
> URL: git://git.kernel.org/pub/scm/git/git.git/
> Pull: master:origin
> Pull: todo:todo
> Pull: maint:maint
> Pull: pu:pu
>
> And the error capture:
>
> jdl@ubuntu:/usr/src/git-core$ git pull origin
> fatal: unexpected EOF
> Fetch failure: git://git.kernel.org/pub/scm/git/git.git/
> jdl@ubuntu:/usr/src/git-core$ git pull origin
> Unpacking 17 objects
> 100% (17/17) done
> * committish: d175455acaaba6bd39dd2d5ec71961bf238f06d4
> branch 'todo' of git://git.kernel.org/pub/scm/git/git
> * refs/heads/todo: same as branch 'todo' of git://git.kernel.org/pub/scm/git/git* committish: 93dcab2937624ebb97f91807576cddb242a55a46
> branch 'maint' of git://git.kernel.org/pub/scm/git/git
> * refs/heads/maint: same as branch 'maint' of git://git.kernel.org/pub/scm/git/git
> * committish: b34403aa97047f90c0cdd5177e63a8e7530e3388
> branch 'master' of git://git.kernel.org/pub/scm/git/git
> * refs/heads/origin: same as branch 'master' of git://git.kernel.org/pub/scm/git/git
> * committish: 6e35634a4d595d554423b04438bfa8b523414c54
> branch 'pu' of git://git.kernel.org/pub/scm/git/git
> * refs/heads/pu: does not fast forward to branch 'pu' of git://git.kernel.org/pub/scm/git/git;
> not updating.
> Already up-to-date.
I noticed this myself this morning. It happened twice, then after leaving it
for a minute or two, it worked. Possibly traffic problems to kernel.org?
I should also report that if a spurious lockfile exists (under cygwin at
least), git just dies with the cryptic "unable to create new cachefile".
Tim.
"I've worked myself up from nothing to a state of supreme poverty."
-- Groucho Marx
next prev parent reply other threads:[~2005-12-01 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 13:42 unexpected EOF? Jon Loeliger
2005-12-01 13:49 ` Tim O'Callaghan [this message]
2005-12-01 18:40 ` Linus Torvalds
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=20051201134917.GH2188@ELSAMSW37164 \
--to=timo@dspsrv.com \
--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).