All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: git clone -l
Date: Tue, 04 Mar 2008 16:32:14 -0800	[thread overview]
Message-ID: <7vd4qa3t9t.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0803041900080.19665@iabervon.org> (Daniel Barkalow's message of "Tue, 4 Mar 2008 19:03:38 -0500 (EST)")

Daniel Barkalow <barkalow@iabervon.org> writes:

> What, exactly, is -l supposed to do for clone? As far as I can tell, we 
> automatically do the local magic if we can. Would it be okay to make 
> "local" default to "if possible", have "-l" mean error if not possible, 
> and have "--no-local" able to avoid using local magic even if we could use 
> it?

It used to be that "-l" meant "When it is local, use hardlink if possible
otherwise copy without complaining, as either are cheaper than the pack
piped to unpack."  Lack of -l meant no local magic.

Recently lack of -l stopped to mean "no local magic".  We still do the
local magic, but we do not do hardlinks and instead do copies.  An "-l"
that asks clone across filesystems still falls back to copying but now
gets a warning.  "--no-hardlinks" does not have any significance anymore,
as that is what you would get for a local clone without -l.

The way to refuse local magic is to use file://$path/ explicitly; we do
not have --no-local.

  reply	other threads:[~2008-03-05  0:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  0:03 git clone -l Daniel Barkalow
2008-03-05  0:32 ` Junio C Hamano [this message]
2008-03-05  0:45   ` Daniel Barkalow
2008-03-05  0:53   ` Brandon Casey

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=7vd4qa3t9t.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.org \
    --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 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.