From: Andreas Krey <a.krey@gmx.de>
To: Git Mailing List <git@vger.kernel.org>
Subject: Remote's 'currently active branch' not HEAD?
Date: Tue, 3 Sep 2013 12:46:52 +0200 [thread overview]
Message-ID: <20130903104652.GA5813@inner.h.apk.li> (raw)
Hi everyone,
I have a strange behaviour from a bare repo I inherited;
when I clone from that one (ssh) the branch checked out
is *not* the one referenced in HEAD in the remote repo,
but apparently some variation of the alphabetically first
or temporally last, or the last *new* branch pushed.
Where would I look to find the reason for this behaviour?
How does git transfer the 'current branch' info during the clone?
There is no 'master' branch in the original bare repo,
but HEAD points to a valid value (refs/heads/r1).
Testing with another repo unfortunately doesn't show any
consistency, more like heisenbuggish.
Andreas
--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
next reply other threads:[~2013-09-03 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 10:46 Andreas Krey [this message]
2013-09-03 11:48 ` Remote's 'currently active branch' not HEAD? Andreas Krey
2013-09-03 12:37 ` Andreas Krey
2013-09-03 13:02 ` Michael Schubert
2013-09-03 13:50 ` Andreas Krey
2013-09-03 15:33 ` Junio C Hamano
2013-09-06 11:41 ` Andreas Krey
2013-09-06 12:54 ` Andreas Krey
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=20130903104652.GA5813@inner.h.apk.li \
--to=a.krey@gmx.de \
--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).