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: Tue, 09 Jan 2024 09:16:43 -0800 [thread overview]
Message-ID: <xmqq1qaqjukk.fsf@gitster.g> (raw)
In-Reply-To: <29D15110-E308-475F-A722-1CDD448CACDA@lemon.garden> (Nathan Manceaux-Panot's message of "Tue, 9 Jan 2024 15:42:13 +0100")
Nathan Manceaux-Panot <fresh.tree3651@lemon.garden> writes:
>> 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!
Documentation/gitformat-index.txt may be a good place to start, of
course.
https://github.com/git/htmldocs/blob/gh-pages/gitformat-index.txt
prev parent reply other threads:[~2024-01-09 17:16 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
2024-01-09 14:42 ` Nathan Manceaux-Panot
2024-01-09 17:16 ` Junio C Hamano [this message]
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=xmqq1qaqjukk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).