From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: git-fetch not working?
Date: Tue, 24 Oct 2006 21:00:45 +0100 [thread overview]
Message-ID: <200610242100.52671.andyparkins@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
Hello,
$ cat .git/remotes/origin
URL: git://git.kernel.org/pub/scm/git/git.git
Pull: refs/heads/master:refs/heads/up/master
Pull: refs/heads/next:refs/heads/up/next
Pull: refs/heads/maint:refs/heads/up/maint
Pull: +refs/heads/pu:refs/heads/up/pu
$ git fetch
fatal: unexpected EOF
Failed to find remote refs
$ ping -c1 git.kernel.org
PING zeus-pub.kernel.org (204.152.191.5) 56(84) bytes of data.
64 bytes from zeus-pub1.kernel.org (204.152.191.5): icmp_seq=1 ttl=54 time=182
ms
Am I doing something wrong?
Andy
--
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-10-24 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 20:00 Andy Parkins [this message]
2006-10-24 20:54 ` git-fetch not working? Petr Baudis
2006-10-24 21:10 ` H. Peter Anvin
2006-10-25 11:11 ` Petr Baudis
2006-10-25 11:37 ` Jakub Narebski
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=200610242100.52671.andyparkins@gmail.com \
--to=andyparkins@gmail.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).