From: Junio C Hamano <gitster@pobox.com>
To: Nathan Manceaux-Panot <fresh.tree3651@lemon.garden>
Cc: git@vger.kernel.org
Subject: Re: Analyzing a corrupted index file
Date: Mon, 08 Jan 2024 11:51:27 -0800 [thread overview]
Message-ID: <xmqqh6jnk3i8.fsf@gitster.g> (raw)
In-Reply-To: <B38C5D82-33E3-4D10-8119-7E0D59DD3DA2@lemon.garden> (Nathan Manceaux-Panot's message of "Sun, 7 Jan 2024 16:22:02 +0100")
Nathan Manceaux-Panot <fresh.tree3651@lemon.garden> writes:
> I have a corrupted git index file, and am trying to read it by
> hand, to understand what's wrong with it. Are there any tools
> that'll let me parse the on-disk, binary version of the index
> file, to unpack it into a human-readable data structure?
"git ls-files" with its various options is probably the closest, but
even the command is not meant for "debugging the bits". It is more
about showing lower-level details of a working index file to help
diagnose the mismatch between end-user expectation and the reality
(e.g. the user says the conflicts were all resolved, an expert asks
to run "ls-files -u" and together they discover that there are paths
that are still unmerged).
next prev parent reply other threads:[~2024-01-08 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 15:22 Analyzing a corrupted index file Nathan Manceaux-Panot
2024-01-08 19:51 ` Junio C Hamano [this message]
2024-01-09 14:42 ` Nathan Manceaux-Panot
2024-01-09 17:16 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqh6jnk3i8.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=fresh.tree3651@lemon.garden \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.