From: Junio C Hamano <gitster@pobox.com>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Technical details about the index file format.
Date: Mon, 11 Feb 2008 11:27:35 -0800 [thread overview]
Message-ID: <7vr6fj8fa0.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1202711335-12026-1-git-send-email-robin.rosenberg@dewire.com> (Robin Rosenberg's message of "Mon, 11 Feb 2008 07:28:55 +0100")
Robin Rosenberg <robin.rosenberg@dewire.com> writes:
> Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
> ---
> Documentation/technical/index-format.txt | 91 ++++++++++++++++++++++++++++++
> 1 files changed, 91 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/technical/index-format.txt
>
> I believe the main index details are accurate. Anything else to explain.
You missed the most important feature. The entries are sorted
in a particular order.
Also I do not think we store CE_UPDATE. The tip of 'master'
will soon clarify about this.
Also when a name is longer than 12-bit can express, we will have
a constant there and the name length could be longer (you need
to strlen() it). The tip of 'master' will soon have this fix
(we used to just overrun).
Other than these, I think the description is fairly accurate.
next prev parent reply other threads:[~2008-02-11 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 6:28 [PATCH] Technical details about the index file format Robin Rosenberg
2008-02-11 12:00 ` Tim Stoakes
2008-02-11 19:27 ` Junio C Hamano [this message]
2010-08-31 0:59 ` Sverre Rabbelier
2010-08-31 7:08 ` Ramkumar Ramachandra
2010-08-31 14:23 ` Jonathan Nieder
2010-08-31 22:12 ` Nguyen Thai Ngoc Duy
2010-09-01 2:28 ` Sverre Rabbelier
2010-09-01 2:52 ` Nguyen Thai Ngoc Duy
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=7vr6fj8fa0.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@dewire.com \
/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).