From: Jakub Narebski <jnareb@gmail.com>
To: Jonathan Chetwynd <j.chetwynd@btinternet.com>
Cc: git@vger.kernel.org
Subject: Re: preserve permissions?
Date: Tue, 04 May 2010 06:08:00 -0700 (PDT) [thread overview]
Message-ID: <m3fx27g6i8.fsf@localhost.localdomain> (raw)
In-Reply-To: <C1288762-C750-4919-A853-5E3229870A59@btinternet.com>
Jonathan Chetwynd <j.chetwynd@btinternet.com> writes:
> git clone ../xsl-test/
>
> the original has a single directory, owner _www, and a few files.
>
> however the clone directory has owner Me.
>
> what is the reason permissions are not preserved?
Why should permissions be preserved? Git is a version control system,
meant mainly for software management, not a backup system.
When you clone repository from somebody, you don't want for files to
have that somebody ownership, especially that such user most probably
do not exist on your machine.
Therefore git does not store ownership, and only basic permissions
(only executable bit for ordinary files, and the symlink bit).
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-05-04 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 12:29 preserve permissions? Jonathan Chetwynd
2010-05-04 13:08 ` Jakub Narebski [this message]
2012-03-03 19:05 ` snk
2012-03-03 19:15 ` Jakub Narebski
2010-05-04 18:44 ` Andrew Keller
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=m3fx27g6i8.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.chetwynd@btinternet.com \
/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.