From: Marc Herbert <Marc.Herbert+news@gmail.com>
To: git@vger.kernel.org
Subject: Re: git clone, hardlinks and multiple users?
Date: Mon, 23 Jan 2012 17:55:37 +0000 [thread overview]
Message-ID: <jfk6up$3dj$1@dough.gmane.org> (raw)
In-Reply-To: <jfc8eh$ck5$1@dough.gmane.org>
On 20/01/2012 17:31, Marc Herbert wrote:
> "git clone" is using hardlinks by default, even when cloning from a
> different user. In such a case the clone ends up with a number of files
> owned by someone else.
>
> Since only immutable objects are cloned this seems to work fine. However
> I would like to know if this "multiple users" case works by chance or by
> specification.
Sorry I meant: "since only immutable objects are HARDLINKED this seems
to work fine".
A few other clarifications following Neal's long answer:
- Yes we are using Linux. But the question is about any filesystem
supporting hardlinks and user permissions.
- My question is only about hardlinks in .git/objects/. Whatever happens
in the checkout is irrelevant.
- I know how to clone with no hardlink and completely avoid the whole
issue. Unfortunately people have this strange habit of using the
simplest/default option, and it does hardlinks.
I guess my rephrased question is: while there is no obvious reason for
git to attempt to touch files in .git/objects/, is there a promise that
this will never, ever happen? Because it would fail in a multi-users config.
The "core.sharedRepository" option is good example. When set to a new
value will it ever try to fix existing objects? That would fail.
prev parent reply other threads:[~2012-01-23 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 17:31 git clone, hardlinks and multiple users? Marc Herbert
2012-01-21 22:54 ` Neal Kreitzinger
2012-01-23 17:55 ` Marc Herbert [this message]
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='jfk6up$3dj$1@dough.gmane.org' \
--to=marc.herbert+news@gmail.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.
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 NNTP newsgroup(s).