From: Teemu Likonen <tlikonen@iki.fi>
To: git@vger.kernel.org
Subject: builtin-remote bug: Stale tracking branch after "git clone"
Date: Fri, 14 Mar 2008 09:51:36 +0200 [thread overview]
Message-ID: <200803140951.36514.tlikonen@iki.fi> (raw)
Hi
I have found a recently added bug. I'm using git version
1.5.4.4.537.gb75aa ('master' branch). I can't describe it technically
so I just type instructions how to reproduce it:
1) Clone some git repository. I think any repo will do.
2) Type "git remote show origin" in that cloned repo. You'll see
something like this:
* remote origin
URL: [...]
Remote branch merged with 'git pull' while on branch master
master
Stale tracking branch (use 'git remote prune')
HEAD
Tracked remote branch
master
$ find .git/refs/remotes
.git/refs/remotes/
.git/refs/remotes/origin
.git/refs/remotes/origin/HEAD
.git/refs/remotes/origin/master
3) As git asked, type "git remote prune origin".
4) Do "git remote show origin" again and it will display this:
* remote origin
URL: [...]
Remote branch merged with 'git pull' while on branch master
master
New remote branch (next fetch will store in remotes/origin)
master [Hmm, interesting]
Seems like .git/refs/remotes/origin/master was deleted:
$ find .git/refs/remotes/
.git/refs/remotes/
.git/refs/remotes/origin
.git/refs/remotes/origin/HEAD
5) Now fetch that "new" remote branch again with "git fetch" and you'll
see this:
error: refs/remotes/origin/HEAD points nowhere!
From [...]
* [new branch] master -> origin/master
6) Now we're back in the beginning. See item 2.
reply other threads:[~2008-03-14 7:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200803140951.36514.tlikonen@iki.fi \
--to=tlikonen@iki.fi \
--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).