git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Geoff Russell" <geoffrey.russell@gmail.com>
To: git@vger.kernel.org
Subject: Problem upgrading to 1.4.0
Date: Sun, 11 Jun 2006 09:37:16 +0930	[thread overview]
Message-ID: <93c3eada0606101707t5eb35a4du3ebd0fd17737943f@mail.gmail.com> (raw)

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 figured these branches were "in the way" so I deleted them:

                git branch -D gb/diffdelta
                etc.

Again "git pull origin" gives the same errors.

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.

I would suggest that when the pull detects the missing remote ref, it
should clean
up the remotes/origin file. Or have I done entirely the wrong thing?

Cheers,
Geoff Russell.

             reply	other threads:[~2006-06-11  0:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-11  0:07 Geoff Russell [this message]
2006-06-11  2:12 ` Problem upgrading to 1.4.0 Junio C Hamano
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=93c3eada0606101707t5eb35a4du3ebd0fd17737943f@mail.gmail.com \
    --to=geoffrey.russell@gmail.com \
    --cc=geoff@austrics.com.au \
    --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).