git/list[1] front-page[2] threads[3] people[4] search[5] about
 

bug report? fatal: Ambiguous object name: 'xxx' during branch operation

From
AIArya Irani <arya.irani@gmail.com>
Date
Mar 6, 2012, 23:18 UTC
Message-ID
<CAB1hNr8-iPbXD-7eEOxZtrJWO78V8sDmwWWQRMMExvtGtpPrhw@mail.gmail.com>
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: Junio C Hamano
Message 1 of 2 in “bug report? fatal: Ambiguous object name: 'xxx' during branch operation”
  1. Arya IraniMar 6, 2012
  2. Junio C HamanoMar 6, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.