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

Re: [PATCH] doc: technical details about the index file format

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Feb 26, 2011, 10:03 UTC
Message-ID
<20110226100310.GA21724@do>
In-Reply-To
<AANLkTi=hz0xRsTy5f8xhzBhu0md_iPCxvdTrEPrzYwzt@mail.gmail.com>
On Sun, Feb 20, 2011 at 04:30:07PM +0700, Nguyen Thai Ngoc Duy wrote:
Show 12 quoted lines
> 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
Previous: Nguyen Thai Ngoc DuyNext: Junio C Hamano
Message 13 of 22 in “doc: technical details about the index file format”
  1. doc: technical details about the index file formatNguyễn Thái Ngọc Duy, Sep 1, 2010
  2. Ramkumar RamachandraSep 1, 2010
  3. Sverre RabbelierSep 1, 2010
  4. Robin RosenbergSep 1, 2010
  5. doc: technical details about the index file formatNguyễn Thái Ngọc Duy, Sep 1, 2010
  6. Alex RiesenSep 2, 2010
  7. Joshua JuranSep 2, 2010
  8. Junio C HamanoSep 2, 2010
  9. Erik Faye-LundSep 2, 2010
  10. doc: technical details about the index file formatNguyễn Thái Ngọc Duy, Sep 6, 2010
  11. Sverre RabbelierFeb 19, 2011
  12. Nguyen Thai Ngoc DuyFeb 20, 2011
  13. Nguyen Thai Ngoc DuyFeb 26, 2011
  14. Junio C HamanoFeb 26, 2011
  15. Nguyen Thai Ngoc DuyFeb 26, 2011
  16. Junio C HamanoMar 2, 2011
  17. Nguyen Thai Ngoc DuyMar 2, 2011
  18. Junio C HamanoMar 2, 2011
  19. Nguyen Thai Ngoc DuyMar 2, 2011
  20. Drew NorthupMar 2, 2011
  21. Nguyen Thai Ngoc DuySep 1, 2010
  22. Robin RosenbergSep 2, 2010

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.