From: Arya Irani <arya.irani@gmail.com>
To: git@vger.kernel.org
Subject: bug report? fatal: Ambiguous object name: 'xxx' during branch operation
Date: Tue, 6 Mar 2012 18:18:40 -0500 [thread overview]
Message-ID: <CAB1hNr8-iPbXD-7eEOxZtrJWO78V8sDmwWWQRMMExvtGtpPrhw@mail.gmail.com> (raw)
In-Reply-To: <CAB1hNr8itJV1-pzWxUo1KPsZNivg+KuRq_5jUwLUyCUpk7k=4w@mail.gmail.com>
If the default start-point for a branch is HEAD, then how can it fail
due to ambiguity? Or what the heck is going on here? :-)
$ git branch -a
* 1.1-SNAPSHOT
master
remotes/1.1-SNAPSHOT
remotes/trunk
$
$ git branch getProviders
warning: refname '1.1-SNAPSHOT' is ambiguous.
fatal: Ambiguous object name: '1.1-SNAPSHOT'.
$
$ cat .git/HEAD
ref: refs/heads/1.1-SNAPSHOT
$
$ git branch getProviders refs/heads/1.1-SNAPSHOT
$
success!
[svn-remote "svn"]
url = https://host/svn/all
fetch = GHIE/maven-projects/hie-util/trunk:refs/remotes/trunk
branches = GHIE/maven-projects/hie-util/branches/*:refs/remotes/*
tags = GHIE/maven-projects/hie-util/tags/*:refs/remotes/tags/*
Thanks,
Arya
P.S. I'll use --prefix for svn to avoid this in the future!
next parent reply other threads:[~2012-03-06 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB1hNr8itJV1-pzWxUo1KPsZNivg+KuRq_5jUwLUyCUpk7k=4w@mail.gmail.com>
2012-03-06 23:18 ` Arya Irani [this message]
2012-03-06 23:44 ` bug report? fatal: Ambiguous object name: 'xxx' during branch operation 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=CAB1hNr8-iPbXD-7eEOxZtrJWO78V8sDmwWWQRMMExvtGtpPrhw@mail.gmail.com \
--to=arya.irani@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.
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).