From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: Geoff Russell <geoffrey.russell@gmail.com>
Subject: Re: Problem upgrading to 1.4.0
Date: Sat, 10 Jun 2006 19:12:25 -0700 [thread overview]
Message-ID: <7v1wtwh246.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <93c3eada0606101707t5eb35a4du3ebd0fd17737943f@mail.gmail.com> (Geoff Russell's message of "Sun, 11 Jun 2006 09:37:16 +0930")
"Geoff Russell" <geoffrey.russell@gmail.com> writes:
> Hi,
>
> When I do a "git pull origin" I get messages:
>
> error: no such remote ref refs/heads/gb/diffdelta
> error: no such remote ref refs/heads/jc/bind
> error: no such remote ref refs/heads/jc/bind-2
> ...
> Fetch failure: git://git.kernel.org/pub/scm/git/git.git
>...
> So I went into .git/remotes/origin and
> removed the lines pointing at these branches and removed the gb and jc
> directories
> and did another git pull and it seems to have worked.
This is the second time this same gotcha caused trouble here. I
agree it would be sensible to make git-fetch (which is called by
git-pull) to detect stale entries in the remotes/origin file and
remote.origin.fetch configuration items.
next prev parent reply other threads:[~2006-06-11 2:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 0:07 Problem upgrading to 1.4.0 Geoff Russell
2006-06-11 2:12 ` Junio C Hamano [this message]
2006-06-13 2:33 ` Pavel Roskin
[not found] ` <20060612224818.383b13ee.seanlkml@sympatico.ca>
2006-06-13 2:48 ` Sean
2006-06-13 3:02 ` Pavel Roskin
2006-06-13 3:28 ` Linus Torvalds
2006-06-13 3:56 ` Pavel Roskin
2006-06-13 7:10 ` Geoff Russell
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=7v1wtwh246.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=geoffrey.russell@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).