Git development
 help / color / mirror / Atom feed
From: Brandon Casey <casey@nrlssc.navy.mil>
To: Junio C Hamano <gitster@pobox.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: git clone -l
Date: Tue, 04 Mar 2008 18:53:37 -0600	[thread overview]
Message-ID: <47CDEF11.8000807@nrlssc.navy.mil> (raw)
In-Reply-To: <7vd4qa3t9t.fsf@gitster.siamese.dyndns.org>

Junio C Hamano wrote:
> 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.

Are you sure?
I thought this was changed by 3d5c418f so that hardlinking is done by default.

  Lack of -l means "do local magic and use hard links".
  Using -l makes git-clone print a warning when hard linking fails.
  --no-hardlinks disables hard linking and still does local magic.

-brandon


      parent reply	other threads:[~2008-03-05  0:54 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
2008-03-05  0:45   ` Daniel Barkalow
2008-03-05  0:53   ` Brandon Casey [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=47CDEF11.8000807@nrlssc.navy.mil \
    --to=casey@nrlssc.navy.mil \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox