From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: Re: confused about preserved permissions
Date: Wed, 22 Aug 2007 14:52:36 +0200 [thread overview]
Message-ID: <46CC3194.764A29D4@eudaptics.com> (raw)
In-Reply-To: 6031FB22-648E-47DE-92EE-2E7255322C27@lrde.epita.fr
Benoit SIGOURE wrote:
> this thread drifted away and although the discussion is interesting,
> the original question hasn't been answered so far and I am in a
> situation where I'd like to know the answer (because my working tree
> needs to be group-readable for a given project and my umask 066 keeps
> annoying me although I don't want to change it).
>
> Someone on IRC pointed me to http://git.or.cz/gitwiki/
> ContentLimitations which says:
>
> "By design, git cannot track other aspects of the filesystem, including:
> * File modes (except for the "executable" bit, and being symbolic
> link)"
>
> That's weird since the file mode is saved in the tree, isn't there a
> way to ask Git to restore this file mode?
At this time, there is not. git tracks only the executable bit. Even
though it stores (and reports) the complete mode, it only ever stores
one of these mode values: 100644, 100755, 120000. Yes, that's an
enormous waste of bits, but that's how it is.
-- Hannes
next prev parent reply other threads:[~2007-08-22 12:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 16:44 confused about preserved permissions martin f krafft
2007-08-20 16:54 ` Pierre Habouzit
2007-08-20 17:38 ` martin f krafft
2007-08-20 17:41 ` Mike Hommey
2007-08-20 17:58 ` David Kastrup
2007-08-20 18:13 ` Mike Hommey
2007-08-20 18:44 ` David Kastrup
[not found] ` <86zm0mgicy.fsf@lola.quinscape.zz>
2007-08-20 18:48 ` Mike Hommey
2007-08-20 19:43 ` Jan Hudec
2007-08-20 19:50 ` Mike Hommey
2007-08-20 20:07 ` Alex Riesen
2007-08-20 20:10 ` Mike Hommey
2007-08-20 20:27 ` Jan Hudec
2007-08-20 20:42 ` David Kastrup
2007-08-20 20:44 ` Mike Hommey
2007-08-20 20:08 ` Jan Hudec
2007-08-20 20:39 ` David Kastrup
2007-08-20 20:50 ` Mike Hommey
2007-08-20 21:03 ` David Kastrup
2007-08-21 1:35 ` Shawn O. Pearce
2007-08-21 2:06 ` Junio C Hamano
2007-08-21 5:34 ` Mike Hommey
2007-08-21 6:04 ` David Kastrup
2007-08-21 18:01 ` René Scharfe
2007-08-21 18:01 ` [PATCH] Documentation: update tar.umask default René Scharfe
2007-08-21 21:15 ` Mike Hommey
2007-08-22 21:03 ` René Scharfe
2007-08-20 18:35 ` confused about preserved permissions Alex Riesen
2007-08-22 12:18 ` Benoit SIGOURE
2007-08-22 12:52 ` Johannes Sixt [this message]
2007-08-22 22:09 ` Junio C Hamano
2007-08-23 6:00 ` martin f krafft
2007-08-23 6:12 ` David Kastrup
2007-08-23 6:23 ` martin f krafft
2007-08-23 7:48 ` Benoit SIGOURE
2007-08-23 7:57 ` Junio C Hamano
2007-08-23 8:08 ` David Kastrup
2007-09-03 18:59 ` Jan Hudec
2007-08-23 7:03 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46CC3194.764A29D4@eudaptics.com \
--to=j.sixt@eudaptics.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).