From: "Simon Holm Thøgersen" <odie@cs.aau.dk>
To: git@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>
Subject: bug related to branches using / in name
Date: Thu, 26 Jun 2008 21:42:30 +0200 [thread overview]
Message-ID: <1214509350.28344.31.camel@odie.local> (raw)
Hi git community
I have a bug report I think is most easily explained by a list of
commands that illustrates the bug.
cd /tmp
mkdir git-bug
cd git-bug
git init
touch foo
git add foo
git commit -a -m '...'
git branch sched
git clone file:///tmp/git-bug /tmp/git-bug-clone
git branch -d sched
git branch sched/urgent
git branch sched/devel
cd /tmp/git-bug-clone
git pull
The last command does not succeed, but produces the following output
error: unable to resolve reference refs/remotes/origin/sched/devel: Not
a directory
>From file:///tmp/git-bug
* [new branch] sched/devel -> origin/sched/devel
error: unable to resolve reference refs/remotes/origin/sched/urgent: Not
a directory
* [new branch] sched/urgent -> origin/sched/urgent
I can work around it by
rm /tmp/git-bug-clone/.git/{,logs/}refs/remotes/origin/sched
but git should take care of this automatically, right?
I'm on git version 1.5.6.
Simon Holm Thøgersen
next reply other threads:[~2008-06-26 20:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 19:42 Simon Holm Thøgersen [this message]
2008-06-27 3:02 ` bug related to branches using / in name Jeff King
2008-06-27 3:04 ` Jeff King
2008-06-27 8:32 ` Simon Holm Thøgersen
2008-06-27 3:57 ` Jeff King
2008-06-27 3:59 ` [PATCH] fetch: report local storage errors in status table Jeff King
2008-06-27 23:37 ` Junio C Hamano
2008-06-28 4:21 ` Jeff King
2008-06-27 4:01 ` [PATCH 2/2] fetch: give a hint to the user when local refs fail to update Jeff King
2008-06-27 23:31 ` bug related to branches using / in name Junio C Hamano
2008-06-28 4:18 ` Jeff King
2008-06-28 4:57 ` Junio C Hamano
2008-06-28 11:42 ` Jakub Narebski
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=1214509350.28344.31.camel@odie.local \
--to=odie@cs.aau.dk \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
/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