From: Duy Nguyen <pclouds@gmail.com>
To: David Abdurachmanov <david.abd@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: "fatal: reference is not a tree:" on git checkout <branch>
Date: Fri, 26 Jul 2013 18:46:38 +0700 [thread overview]
Message-ID: <CACsJy8BWnrH2J+BhG09BpfzMUFw=-XirP7EAa3QKuXtbvQr18Q@mail.gmail.com> (raw)
In-Reply-To: <CC257523-1C84-4F73-9AB0-D1B5A5ECDC45@gmail.com>
On Fri, Jul 26, 2013 at 4:52 PM, David Abdurachmanov
<david.abd@gmail.com> wrote:
> Hi,
>
> Reproduce:
>
> $ git clone https://github.com/cms-sw/cmsdist.git
> $ git branch -a | grep devel-gcc48
> remotes/origin/IB/CMSSW_7_0_X/devel-gcc48
> $ git checkout IB/CMSSW_7_0_X/devel-gcc48
> fatal: reference is not a tree: IB/CMSSW_7_0_X/devel-gcc48
>
> It has stopped to work with the last pull request. All the references on Google
> talk about submodules, which I don't use. Any ideas what could be causing this
> issue?
"Bad" naming. It interprets the branch name as something-gHEX like the
output from git-describe. Coincidently "cc48" is an umambiguous short
sha-1. check_tracking_name, which prefix "origin/" in, never has a
chance to run.
We should probably check in get_describe_name() that the returned
value is a commit or a tag, but that doesn't really solve the problem.
I think check_tracking_name should have higher priority than
get_describe_name()..
--
Duy
prev parent reply other threads:[~2013-07-26 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 9:52 "fatal: reference is not a tree:" on git checkout <branch> David Abdurachmanov
2013-07-26 11:46 ` Duy Nguyen [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8BWnrH2J+BhG09BpfzMUFw=-XirP7EAa3QKuXtbvQr18Q@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=david.abd@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).