From: "Jens Lindström" <jl@opera.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, johan@herland.net
Subject: Re: [PATCH] clone: Skip pack-*.keep files when cloning locally
Date: Wed, 3 Jul 2013 12:02:49 +0200 [thread overview]
Message-ID: <CAEef6WxnRbPVFgZP4asQrvYGVTTbGzeQCwPJrwj4a-6k9vFcbQ@mail.gmail.com> (raw)
In-Reply-To: <7vip0ui757.fsf@alter.siamese.dyndns.org>
On Mon, Jul 1, 2013 at 6:20 PM, Junio C Hamano <gitster@pobox.com> wrote:
> I am not sure if we should care that deeply about them in the first
> place.
Fine by me; I don't really have a strong opinion on the matter.
> Besides, I think you can make a hardlink to a file that you cannot
> read.
Not always. The Linux kernel can at least be configured not to allow
it. It seems this is enabled by default in at least Debian.
This restriction had me a bit confused when I was testing variations
here; I expected all "access denied" failures to be because of .keep
files, but in fact creating hardlinks to other files (.idx and .pack)
failed too, even though they were readable. This caused "git clone
--local" to fail, while "git clone" succeeded after falling back to
copying instead of linking.
next prev parent reply other threads:[~2013-07-03 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 14:42 [PATCH] clone: Skip pack-*.keep files when cloning locally Jens Lindstrom
2013-06-28 18:38 ` Junio C Hamano
2013-06-28 20:38 ` Junio C Hamano
2013-07-01 10:24 ` Jens Lindström
2013-07-01 16:20 ` Junio C Hamano
2013-07-03 10:02 ` Jens Lindström [this message]
2013-07-03 17:26 ` Junio C Hamano
2013-07-03 18:31 ` Jens Lindström
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEef6WxnRbPVFgZP4asQrvYGVTTbGzeQCwPJrwj4a-6k9vFcbQ@mail.gmail.com \
--to=jl@opera.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).