git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>,
	git@vger.kernel.org, Daniel Barkalow <barkalow@iabervon.org>,
	gitster@pobox.com
Subject: Re: [PATCH 1/2] clone: do not ignore --no-hardlinks
Date: Thu, 26 Feb 2009 23:24:47 -0800	[thread overview]
Message-ID: <7vy6vsmjeo.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090227025829.GA22060@coredump.intra.peff.net> (Jeff King's message of "Thu, 26 Feb 2009 21:58:29 -0500")

Jeff King <peff@peff.net> writes:

> On Fri, Feb 27, 2009 at 12:31:22AM +0100, Johannes Schindelin wrote:
>
>> Somehow --no-hardlinks got broken by making clone a builtin.  This
>> was discovered during my work on --depth being ignored for local
>> clones.
>> 
>> There will be a test case that tests for --no-hardlinks in conjunction
>> with --depth, so this patch is not accompanied by a separate test.
>
> Hmm. But --no-hardlinks has an effect later, in copy_or_link_directory,
> making it just do a copy. So it _does_ work, just not in the way you
> expect.

Yup, I agree.

> I think to turn off local shortcuts entirely, --no-local would probably
> make more sense. IOW, something like this:

So across filesystems:

 - "git clone /p/a/t/h" falls back to copying;

 - "git clone --local /p/a/t/h" should fail without falling back to
   copying; and

 - "git clone --no-local /p/a/t/h" should work as if file:///p/a/t/h
   was given.

That is much more sensible than making "git clone --no-hardlinks /p/a/t/h"
imply more than what the option really means: we are making a local copy
but do not cheat with hardlinking.

  reply	other threads:[~2009-02-27  7:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1235672273u.git.johannes.schindelin@gmx.de>
2009-02-26 18:20 ` [PATCH] clone: ignore --depth when cloning locally (implicitly --local) Johannes Schindelin
2009-02-26 22:45   ` Junio C Hamano
2009-02-26 22:55     ` Johannes Schindelin
2009-02-26 23:31       ` [PATCH 0/2] shallow clone stuff Johannes Schindelin
2009-02-27  0:35         ` Junio C Hamano
2009-02-26 23:31       ` [PATCH 1/2] clone: do not ignore --no-hardlinks Johannes Schindelin
2009-02-27  2:58         ` Jeff King
2009-02-27  7:24           ` Junio C Hamano [this message]
2009-02-27  7:59             ` Junio C Hamano
2009-02-27  8:13               ` Junio C Hamano
2009-02-27 16:54                 ` Daniel Barkalow
2009-02-27 11:35               ` Jeff King
2009-02-26 23:31       ` [PATCH 2/2] clone: ignore --depth when cloning locally (implicitly --local) Johannes Schindelin

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=7vy6vsmjeo.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=peff@peff.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.
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).