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

Re: fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.

From
CBcarbonated beverage <ramune@net-ronin.org>
Date
Jun 10, 2007, 08:54 UTC
Message-ID
<20070610085430.GA17255@prophet.net-ronin.org>
In-Reply-To
<7vk5uekagd.fsf@assigned-by-dhcp.cox.net>
On Fri, Jun 08, 2007 at 03:27:30AM -0700, Junio C Hamano wrote:
> How did you get your repository into such a state to begin with?
It's kinda odd to see this thread, as I hit this issue today, as well.
If you need another test case, the cvsps git repo shows this too:

ramune/lycaeum:git: git clone http://ydirson.free.fr/soft/git/cvsps.git <snip checkout messages> ramune/lycaeum:git: cd cvsps ramune/lycaeum:cvsps: ls ramune/lycaeum:cvsps: git checkout -f warning: You appear to be on a branch yet to be born. warning: Forcing checkout of HEAD. fatal: just how do you expect me to merge 0 trees? ramune/lycaeum:cvsps: cat .git/HEAD ref: refs/heads/master ramune/lycaeum:cvsps: ls .git/refs/head/master ls: .git/refs/head/master: No such file or directory

-- DN Daniel

Previous: Junio C Hamano
Message 7 of 7 in “fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.”
  1. Thomas GlanzmannJun 8, 2007
  2. Junio C HamanoJun 8, 2007
  3. Thomas GlanzmannJun 8, 2007
  4. Junio C HamanoJun 8, 2007
  5. Thomas GlanzmannJun 8, 2007
  6. Junio C HamanoJun 8, 2007
  7. carbonated beverageJun 10, 2007

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.