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

Re: corrupted Git repository

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Jun 21, 2011, 13:47 UTC
Message-ID
<4E00A0E1.8000006@viscovery.net>
In-Reply-To
<BANLkTi=GdEfXnAGa6V-33wqX2C-2x-9JQQ@mail.gmail.com>
Am 6/21/2011 12:10, schrieb Kasra Khosoussi:
> Everything seems fine now

But it would still be good to know how the corruption could have happened. Do you have any clues?

Disk full? Ctrl-C in the middle of a git operation? Some cron script interference (unlikely)? Permission problems (unlikely)? Networking problems (only if the repository is on a network mount)? Something else?

-- Hannes
Previous: Kasra KhosoussiNext: Kasra Khosoussi
Message 8 of 11 in “corrupted Git repository”
  1. Kasra KhosoussiJun 21, 2011
  2. Michael J GruberJun 21, 2011
  3. Kasra KhosoussiJun 21, 2011
  4. Michael J GruberJun 21, 2011
  5. Kasra KhosoussiJun 21, 2011
  6. Ilari LiusvaaraJun 21, 2011
  7. Kasra KhosoussiJun 21, 2011
  8. Johannes SixtJun 21, 2011
  9. Kasra KhosoussiJun 21, 2011
  10. Carlos Martín NietoJun 21, 2011
  11. Kasra KhosoussiJun 21, 2011

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.