From: Junio C Hamano <gitster@pobox.com>
To: jidanni@jidanni.org
Cc: git@vger.kernel.org
Subject: Re: why not preserve file permissions?
Date: Fri, 05 Dec 2008 14:38:41 -0800 [thread overview]
Message-ID: <7vljuuxn66.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <87tz9igzbr.fsf@jidanni.org> (jidanni@jidanni.org's message of "Sat, 06 Dec 2008 04:08:08 +0800")
jidanni@jidanni.org writes:
> 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
Actually in a very early days, git used to record the full (mode & 0777)
for blobs.
Once people started using git, everybody realized that it had a very
unpleasant side effect that the resulting tree depended on user's umasks,
because one person records a blob with mode 664 and the next person who
modifies the file would record with mode 644, and it made it very hard to
keep track of meaningful changes to the source code. This issue was fixed
long time ago with commit e447947 (Be much more liberal about the file
mode bits., 2005-04-16).
next prev parent reply other threads:[~2008-12-05 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 20:08 why not preserve file permissions? jidanni
2008-12-05 22:23 ` Jakub Narebski
2008-12-05 22:38 ` Junio C Hamano [this message]
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=7vljuuxn66.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jidanni@jidanni.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox