From: Uwe Zeisberger <zeisberg@informatik.uni-freiburg.de>
To: git@vger.kernel.org
Subject: HEAD branch duplicated in remotes/origin
Date: Thu, 8 Jun 2006 09:38:57 +0200 [thread overview]
Message-ID: <20060608073857.GA5072@informatik.uni-freiburg.de> (raw)
Hello,
when cloning with --use-separate-remote, $GITDIR/remotes/origin contains
two references to refs/heads/master. This breaks `git fetch origin'.
uzeisberger@io:~/gsrc$ git --version
git version 1.4.0.rc2.ga95e
uzeisberger@io:~/gsrc$ git clone --use-separate-remote git://git.kernel.org/pub/scm/git/git.git git-copy
Checking files out...)
100% (523/523) done
uzeisberger@io:~/gsrc$ cd git-copy
uzeisberger@io:~/gsrc/git-copy$ git fetch origin
error: no such remote ref refs/heads/master
Fetch failure: git://git.kernel.org/pub/scm/git/git.git
uzeisberger@io:~/gsrc/git-copy$ grep -n master .git/remotes/origin
2:Pull: refs/heads/master:refs/remotes/origin/master
12:Pull: refs/heads/master:refs/remotes/origin/master
uzeisberger@io:~/gsrc/git-copy$ sed -i 2d .git/remotes/origin
uzeisberger@io:~/gsrc/git-copy$ git fetch origin
uzeisberger@io:~/gsrc/git-copy$
I didn't look into it deeply, but I think this happens because the
remote HEAD is translated to refs/heads/master and added while master is
added once more while processing refs/heads/master explicitly.
Best regards
Uwe
--
Uwe Zeisberger
http://www.google.com/search?q=12+divided+by+3
next reply other threads:[~2006-06-08 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 7:38 Uwe Zeisberger [this message]
2006-06-08 8:17 ` HEAD branch duplicated in remotes/origin Junio C Hamano
2006-06-08 12:33 ` Uwe Zeisberger
2006-06-08 16:39 ` Junio C Hamano
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=20060608073857.GA5072@informatik.uni-freiburg.de \
--to=zeisberg@informatik.uni-freiburg.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).