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

Re: Analyzing a corrupted index file

From
NMNathan Manceaux-Panot <fresh.tree3651@lemon.garden>
Date
Jan 9, 2024, 14:42 UTC
Message-ID
<29D15110-E308-475F-A722-1CDD448CACDA@lemon.garden>
In-Reply-To
<xmqqh6jnk3i8.fsf@gitster.g>
> On Jan 8, 2024, at 20:51, Junio C Hamano <gitster@pobox.com> wrote:
> 
> "git ls-files" with its various options is probably the closest, but
> even the command is not meant for "debugging the bits"
Thanks for the pointer. In the meantime I've started to make sense of the binary representation, against all odds, so there's hope for me there!
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 4 in “Analyzing a corrupted index file”
  1. Nathan Manceaux-PanotJan 7, 2024
  2. Junio C HamanoJan 8, 2024
  3. Nathan Manceaux-PanotJan 9, 2024
  4. Junio C HamanoJan 9, 2024

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.