From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Git files data formats documentation
Date: Sat, 05 Aug 2006 14:56:42 -0700 [thread overview]
Message-ID: <44D5141A.2070004@gmail.com> (raw)
In-Reply-To: <7vac6jfzem.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
...
>> <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.
>> ;
>
> It's not really "by default" -- more like "by definition", since
> there is no way for the program to use something different. We
> used to record non-canonical modes in ancient versions of git,
> but I think fsck-objects would warn on objects created that way.
>
See git-mktree.
next prev parent reply other threads:[~2006-08-05 21:56 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 [this message]
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
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=44D5141A.2070004@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).