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

Re: corrupt object on git-gc

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Nov 9, 2007, 15:34 UTC
Message-ID
<47347E0E.1040205@viscovery.net>
In-Reply-To
<4fe79b4b0711090701g7a43cdfdi5e20e5ffb437d7bb@mail.gmail.com>
Yossi Leybovich schrieb:
> [about corrupt loose object '4b9458b3786228369c63936db65827de3cc06200']

You can try to create a clone (after you have fixed up the artificial breakages that you made). If that goes well, then the bad object is referenced only from reflogs.

-- Hannes
Previous: Yossi LeybovichNext: Yossi Leybovich
Message 4 of 20 in “Re: corrupt object on git-gc”
  1. Yossi LeybovichNov 9, 2007
  2. Andreas EricssonNov 9, 2007
  3. Yossi LeybovichNov 9, 2007
  4. Johannes SixtNov 9, 2007
  5. Yossi LeybovichNov 9, 2007
  6. Johannes SixtNov 9, 2007
  7. Nicolas PitreNov 9, 2007
  8. Yossi LeybovichNov 9, 2007
  9. Nicolas PitreNov 9, 2007
  10. Linus TorvaldsNov 9, 2007
  11. add a howto document about corrupted blob recoveryNicolas Pitre, Nov 9, 2007
  12. Johannes SchindelinNov 9, 2007
  13. J. Bruce FieldsNov 26, 2007
  14. Yossi LeybovichNov 9, 2007
  15. Linus TorvaldsNov 9, 2007
  16. Yossi LeybovichNov 9, 2007
  17. Linus TorvaldsNov 9, 2007
  18. Mike HommeyNov 9, 2007
  19. Yossi LeybovichNov 9, 2007
  20. Mike HommeyNov 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.