From: jidanni@jidanni.org
To: git@vger.kernel.org
Subject: why not preserve file permissions?
Date: Sat, 06 Dec 2008 04:08:08 +0800 [thread overview]
Message-ID: <87tz9igzbr.fsf@jidanni.org> (raw)
Why not preserve permissions the way you find them, instead of just
using 644 and 755? It certainly couldn't be more complicated than what
you are doing now, and that way one could do things like use git to
update system administration files across a sneakernet containing e.g.,
# dlocate -lsconf exim4-config|sed 's/ .*//'|sort -u
-rw-r-----
-rw-r--r--
-rwxr-xr-x
> git was made for tracking source code, not 640 files.
On the sneakernet no public patches would be sent, and the
administrator would remember to make the sensitive .git directories
700. And sure, git should enforce umask or no set-uid or whatever when
doing a checkout etc. The deluxe edition of git could even print a
warning: "you are trying to track a 640 file but your .git permissions
are less restrictive." However I recommend no premium or deluxe
editions for now.
> Patches welcome.
Trust me, you don't want "grandpa who forgot the parking brake"
anywhere near your code.
next reply other threads:[~2008-12-05 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 20:08 jidanni [this message]
2008-12-05 22:23 ` why not preserve file permissions? Jakub Narebski
2008-12-05 22:38 ` Junio C Hamano
2008-12-06 1:29 ` Jeff King
2008-12-06 0:05 ` Daniel Barkalow
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=87tz9igzbr.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--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.
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.