All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Git files data formats documentation
Date: Sat, 05 Aug 2006 20:41:32 +0200	[thread overview]
Message-ID: <eb2onf$7up$1@sea.gmane.org> (raw)
In-Reply-To: 44D42F0D.3040707@gmail.com

A Large Angry SCM wrote:

> <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>
>         ;
[...]
> <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>).

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  parent reply	other threads:[~2006-08-05 18:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-05  5:39 Git files data formats documentation A Large Angry SCM
2006-08-05  5:48 ` Jon Smirl
2006-08-05  6:51 ` Junio C Hamano
2006-08-05 19:30   ` Shawn Pearce
2006-08-05 21:56   ` A Large Angry SCM
2006-08-06  0:37     ` Junio C Hamano
2006-08-05 16:22 ` Shawn Pearce
2006-08-05 17:31   ` A Large Angry SCM
2006-08-05 18:41 ` Jakub Narebski [this message]
2006-08-05 20:15   ` A Large Angry SCM
2006-08-05 23:43     ` Jakub Narebski
2006-08-05 22:35 ` A Large Angry SCM
2006-08-16 16:55   ` Nicolas Pitre

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='eb2onf$7up$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /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.