From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, kusmabite@gmail.com, raa.lkml@gmail.com,
jjuran@gmail.com, Robin Rosenberg <robin.rosenberg@dewire.com>
Subject: Re: [PATCH] doc: technical details about the index file format
Date: Sat, 26 Feb 2011 17:03:10 +0700 [thread overview]
Message-ID: <20110226100310.GA21724@do> (raw)
In-Reply-To: <AANLkTi=hz0xRsTy5f8xhzBhu0md_iPCxvdTrEPrzYwzt@mail.gmail.com>
On Sun, Feb 20, 2011 at 04:30:07PM +0700, Nguyen Thai Ngoc Duy wrote:
> 2011/2/20 Sverre Rabbelier <srabbelier@gmail.com>:
> > Heya,
> >
> > 2010/9/6 Nguyễn Thái Ngọc Duy <pclouds@gmail.com>:
> >> This bases on the original work by Robin Rosenberg.
> >
> > Junio, in the "what's cooking" you mention that you might jump in to
> > improve this? Duy, are you still interested in carrying this forward?
> > This patch [0] would be helpful to the hgit people as well :).
>
> I can try to study resolve undo extension next week and see if I can
> write it down in the document.
OK here come the missing bits on top of the previous patch. Looks good?
--8<--
diff --git a/Documentation/technical/index-format.txt b/Documentation/technical/index-format.txt
index 5b1d70d..574eb3b 100644
--- a/Documentation/technical/index-format.txt
+++ b/Documentation/technical/index-format.txt
@@ -118,7 +118,7 @@ GIT index format
=== Tree cache
Tree cache extension contains pre-computes hashes for all trees that
- can be derived from the index
+ can be derived from the index.
- Extension tag { 'T', 'R', 'E', 'E' }
@@ -137,8 +137,20 @@ GIT index format
=== Resolve undo
- TODO
+ Resolve undo extension records staged entries before they are
+ resolved and removed from index. It can be used to recreate conflicts
+ after the conflict is incorrectly resolved.
- Extension tag { 'R', 'E', 'U', 'C' }
- 32-bit size
+
+ - A number of entries
+
+ NUL-terminated entry name
+
+ Entry mode of the entry in three stages, in increasing order from
+ 1 to 3, in NUL-terminated ASCII octal number.
+
+ 160 bit SHA-1 of the entry in three stages, in increasing
+ order from 1 to 3. A stage with zero mode will be skipped.
-->8--
--
Duy
next prev parent reply other threads:[~2011-02-26 10:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 9:53 [PATCH] doc: technical details about the index file format Nguyễn Thái Ngọc Duy
2010-09-01 10:36 ` Ramkumar Ramachandra
2010-09-01 15:20 ` Sverre Rabbelier
2010-09-01 18:54 ` Robin Rosenberg
2010-09-01 14:39 ` Nguyễn Thái Ngọc Duy
2010-09-02 8:56 ` Alex Riesen
2010-09-02 9:08 ` Joshua Juran
2010-09-02 14:50 ` Junio C Hamano
2010-09-02 15:11 ` Erik Faye-Lund
2010-09-06 10:37 ` Nguyễn Thái Ngọc Duy
2011-02-19 22:16 ` Sverre Rabbelier
2011-02-20 9:30 ` Nguyen Thai Ngoc Duy
2011-02-26 10:03 ` Nguyen Thai Ngoc Duy [this message]
2011-02-26 10:23 ` Junio C Hamano
2011-02-26 13:36 ` Nguyen Thai Ngoc Duy
2011-03-02 1:51 ` Junio C Hamano
2011-03-02 3:34 ` Nguyen Thai Ngoc Duy
2011-03-02 6:02 ` Junio C Hamano
2011-03-02 11:43 ` Nguyen Thai Ngoc Duy
2011-03-02 12:53 ` Drew Northup
2010-09-01 23:28 ` Nguyen Thai Ngoc Duy
2010-09-02 5:59 ` Robin Rosenberg
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=20110226100310.GA21724@do \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jjuran@gmail.com \
--cc=kusmabite@gmail.com \
--cc=raa.lkml@gmail.com \
--cc=robin.rosenberg@dewire.com \
--cc=srabbelier@gmail.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 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.