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

Re: Git files data formats documentation

From
Jakub Narebski <jnareb@gmail.com>
Date
Aug 5, 2006, 23:43 UTC
Message-ID
<eb3ad8$fq6$1@sea.gmane.org>
In-Reply-To
<44D4FC52.6030807@gmail.com>
A Large Angry SCM wrote:
> Jakub Narebski wrote:
Show 6 quoted lines
>> I do wonder why there is <OCTAL_MODE> (and not <BINARY_OCTAL_MODE>) 
>> but <BINARY_OBJ_ID> (and not <HEX_OBJ_ID>).
>> 
> 
> <OCTAL_MODE> because it's an ASCII string. <BINARY_OBJ_ID> because it's 
> the 20 byte digest.

I meant why git use ASCII string for octal mode, while using 20 byte digest for object-id in tree format. More consistent would be use binary and binary, or ASCII and ASCII (i.e. <HEX_OBJ_ID>).

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: A Large Angry SCMNext: A Large Angry SCM
Message 11 of 13 in “Git files data formats documentation”
  1. A Large Angry SCMAug 5, 2006
  2. Jon SmirlAug 5, 2006
  3. Junio C HamanoAug 5, 2006
  4. Shawn PearceAug 5, 2006
  5. A Large Angry SCMAug 5, 2006
  6. Junio C HamanoAug 6, 2006
  7. Shawn PearceAug 5, 2006
  8. A Large Angry SCMAug 5, 2006
  9. Jakub NarebskiAug 5, 2006
  10. A Large Angry SCMAug 5, 2006
  11. Jakub NarebskiAug 5, 2006
  12. A Large Angry SCMAug 5, 2006
  13. Nicolas PitreAug 16, 2006

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.