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

Fatal error running status in new repo

From
Jacob Helwig <jacob.helwig@gmail.com>
Date
Feb 16, 2010, 04:19 UTC
Message-ID
<20100216041945.GB10296@vfb-9.home>
I just noticed this when creating a new repo for a project.

$ mkdir tmp $ cd tmp $ git init Initialized empty shared Git repository in /home/jhe/projects/tmp/.git/ $ git status # On branch master # # Initial commit # warning: ignoring dangling symref HEAD. fatal: bad revision 'HEAD' nothing to commit (create/copy files and use "git add" to track) $ echo $? 0 $ git --version git version 1.7.0

Seems a bit silly that "git status" should be issuing warnings, and fatal errors (especially when the exit code is still 0), when run before the first commit has been created in a brand new repository.

The warnings make sense if you know what's going on behind the scenes, but seem like the kind of thing that could scare someone new to git when they haven't actually done anything wrong at this point.

-- 
Jacob Helwig
Next: Jeff King
Message 1 of 8 in “Fatal error running status in new repo”
  1. Jacob HelwigFeb 16, 2010
  2. Jeff KingFeb 16, 2010
  3. Jacob HelwigFeb 16, 2010
  4. Jeff KingFeb 16, 2010
  5. dwim_ref: fix dangling symref warningJeff King, Feb 16, 2010
  6. Jeff KingFeb 16, 2010
  7. submodule summary: Don't barf when invoked in an empty repoJohan Herland, Feb 16, 2010
  8. Jeff KingFeb 17, 2010

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.