Thread (9 messages) flat view 9 messages, 5 authors, 2016-06-15

Re: Git files data formats documentation

From: A Large Angry SCM <hidden>
Date: 2016-06-15 22:42:35

Jakub Narebski wrote:
A Large Angry SCM wrote:
quoted
<TREE_ENTRY>
        # The type of the object referenced MUST be appropriate for
        # the mode. Regular files and symbolic links reference a BLOB
        # and directories reference a TREE.
        :       <OCTAL_MODE> <SP> <NAME> <NUL> <BINARY_OBJ_ID>
        ;
[...]
quoted
<OCTAL_MODE>
        # Octal encoding, without prefix, of the file system object
        # type and permission bits. The bit layout is according to the
        # POSIX standard, with only regular files, directories, and
        # symbolic links permitted. The actual permission bits are
        # all zero except for regular files. The only permission bit
        # of any consequence to Git is the owner executable bit. By
        # default, the permission bits for files will be either 0644
        # or 0755, depending on the owner executable bit.
        ;
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help