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

Re: git-log fatal error in empty repo

From
GBGeert Bosch <bosch@adacore.com>
Date
Jun 9, 2007, 02:31 UTC
Message-ID
<9EDDBC9D-EE20-4158-AF77-E46B1DD0BC74@adacore.com>
In-Reply-To
<7vps47o6eh.fsf@assigned-by-dhcp.cox.net>
On Jun 7, 2007, at 16:29, Junio C Hamano wrote:
> Maybe, but I highly doubt if it is worth to bother about it.

My first confusion with git was exactly this issue. It's very normal for a new user to do a git init and than try to verify that the current state is a sane empty repository.

So, git log, git status and git fsck should all properly handle this situation and give reasonable output in this case.

   -Geert
Previous: Junio C Hamano
Message 3 of 3 in “git-log fatal error in empty repo”
  1. Steve HoelzerJun 7, 2007
  2. Junio C HamanoJun 7, 2007
  3. Geert BoschJun 9, 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.