On Aug 20, 2007, at 6:44 PM, martin f krafft wrote:
Hello, I am a bit confused about how git stores and restores permissions.
[...]
And is there a way to tell git not to mess with the permissions in the worktree when switching branches? I am not sure what's causing it since the inode of files does not seem to change, so git apparently explicitly fchmod()'s files. I'd be grateful for any documentation to read in addition to the code. I saw core.filemode, but that's only about the x bit, it seems. Thanks,
Hi,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?
Cheers, -- Benoit Sigoure aka Tsuna EPITA Research and Development Laboratory
Attachment:
PGP.sig
Description: This is a digitally signed message part
