From: Paul Jackson <pj@sgi.com>
To: Martin Mares <mj@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: Storing permissions
Date: Sat, 16 Apr 2005 16:19:35 -0700 [thread overview]
Message-ID: <20050416161935.0d2cf3b0.pj@sgi.com> (raw)
In-Reply-To: <20050416230058.GA10983@ucw.cz>
Martin wrote:
> Does it really make sense to store full permissions in the trees? I think
> that remembering the x-bit should be good enough for almost all purposes
> and the other permissions should be left to the local environment.
That matches my experience - store 1 bit of mode state - executable or not.
Let local environment determine read, write and umask permissions.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401
next prev parent reply other threads:[~2005-04-16 23:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 23:00 Storing permissions Martin Mares
2005-04-16 23:19 ` Paul Jackson [this message]
2005-04-16 23:42 ` Junio C Hamano
2005-04-17 0:03 ` Paul Jackson
2005-04-17 5:00 ` David A. Wheeler
2005-04-17 1:01 ` Morten Welinder
2005-04-17 1:30 ` Paul Jackson
2005-04-17 4:48 ` Linus Torvalds
2005-04-17 5:32 ` Paul Jackson
2005-04-17 5:37 ` Linus Torvalds
2005-04-17 6:22 ` David A. Wheeler
2005-04-17 8:13 ` Paul Jackson
2005-04-17 14:51 ` Daniel Barkalow
2005-04-17 16:10 ` Linus Torvalds
2005-04-17 16:21 ` David A. Wheeler
2005-04-17 22:15 ` Symlinks [was Re: Storing permissions] Morten Welinder
2005-12-07 14:56 ` dotfile support Zack Brown
2005-12-07 15:28 ` Andreas Ericsson
2005-12-07 16:11 ` Zack Brown
2005-12-07 21:51 ` Petr Baudis
2005-12-07 15:43 ` Johannes Schindelin
2005-12-07 17:43 ` Junio C Hamano
2005-12-07 18:19 ` Zack Brown
2005-12-07 19:05 ` Junio C Hamano
2005-12-08 0:47 ` H. Peter Anvin
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=20050416161935.0d2cf3b0.pj@sgi.com \
--to=pj@sgi.com \
--cc=git@vger.kernel.org \
--cc=mj@ucw.cz \
/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).