From: Teemu Likonen <tlikonen@iki.fi>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: remote/clone bug: Stale tracking branch HEAD
Date: Sun, 16 Mar 2008 19:21:49 +0200 [thread overview]
Message-ID: <200803161921.49274.tlikonen@iki.fi> (raw)
In-Reply-To: <7v1w6bj7f9.fsf_-_@gitster.siamese.dyndns.org>
Junio C Hamano kirjoitti:
> We are going into 1.5.5-rc feature freeze tonight, and squashing
> these bugs now are of the highest priority. Please keep the bug
> reports and fixes flowing.
I hope this bug won't find it's way to the release:
http://article.gmane.org/gmane.comp.version-control.git/77188
In short: After 'git clone' the command 'git remote show origin' shows a
stale tracking branch HEAD:
Stale tracking branch (use 'git remote prune')
HEAD
'git remote prune origin' removes branch 'master'; you can see this
with "git remote show origin":
New remote branch (next fetch will store in remotes/origin)
master
'git fetch' fetches 'master' again but the stale tracking branch HEAD
appears again.
next prev parent reply other threads:[~2008-03-16 17:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 13:05 git remote --mirror bug? Joakim Tjernlund
2008-03-15 18:08 ` Joakim Tjernlund
2008-03-16 10:21 ` Re* " Junio C Hamano
2008-03-16 17:21 ` Teemu Likonen [this message]
2008-03-16 22:24 ` On fetch refspecs and wildcards Junio C Hamano
2008-03-16 22:33 ` Junio C Hamano
2008-03-16 23:03 ` Daniel Barkalow
2008-03-17 0:14 ` Junio C Hamano
2008-03-17 2:14 ` Daniel Barkalow
2008-03-18 14:04 ` Re* git remote --mirror bug? Johannes Schindelin
2008-03-18 19:02 ` Junio C Hamano
2008-03-19 0:35 ` Johannes Schindelin
2008-03-28 6:16 ` [PATCH/RFC] Allow "git remote --mirror" to mirror stashes Junio C Hamano
2008-03-28 15:45 ` Daniel Barkalow
2008-03-31 0:19 ` Junio C Hamano
2008-03-31 3:03 ` Daniel Barkalow
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=200803161921.49274.tlikonen@iki.fi \
--to=tlikonen@iki.fi \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).