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

Re: [HELP] Corrupted repository

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Jun 21, 2013, 19:15 UTC
Message-ID
<CALkWK0kLmdbooWUw-x+TBk-fB_XDFQzyu6Q8yb1Prsgi3FD67A@mail.gmail.com>
In-Reply-To
<7vzjujl267.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> A tl;dr is that we _trust_ our refs and everything reachable from
> them has to be complete.  If that is not the case, things will not
> work, and it is not a priority to add workarounds in the normal
> codepath to slow things down.
Makes sense.
> That does not forbid an addition of "git recover-corrupted-repo"
> command, whose "assume everything might be broken" code is not
> shared with the fastpath of other commands.

I'm not looking for a kitchen-sink command: I'm looking for a well-documented toolset to precisely fix corruptions. We have some corruption tests in our testsuite already: I think I'll start digging there.

Thanks.
Previous: Junio C HamanoNext: Matthieu Moy
Message 5 of 6 in “[HELP] Corrupted repository”
  1. Ramkumar RamachandraJun 21, 2013
  2. Junio C HamanoJun 21, 2013
  3. Ramkumar RamachandraJun 21, 2013
  4. Junio C HamanoJun 21, 2013
  5. Ramkumar RamachandraJun 21, 2013
  6. Matthieu MoyJun 23, 2013

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.