From: Morten Welinder <mwelinder@gmail.com>
To: Martin Mares <mj@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: Storing permissions
Date: Sat, 16 Apr 2005 21:01:35 -0400 [thread overview]
Message-ID: <118833cc05041618017fb32a2@mail.gmail.com> (raw)
In-Reply-To: <20050416230058.GA10983@ucw.cz>
> 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.
It makes some sense in principle, but without storing what they mean
(i.e., group==?) it certainly makes no sense. It's a bit like unpacking a
tar file.
I suspect a non-readable file would cause a bit of a problem in the low-level
commands.
Morten
next prev parent reply other threads:[~2005-04-17 0:57 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
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 [this message]
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=118833cc05041618017fb32a2@mail.gmail.com \
--to=mwelinder@gmail.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 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.