public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <gitster@pobox•com>
To: "Albert L. Lash\, IV" <albert.lash@gmail•com>
Cc: git@vger•kernel.org, "Albert L. Lash\, IV" <alash3@bloomberg•net>
Subject: Re: [PATCH 3/4] docs/git-clone: clarify use of --no-hardlinks option
Date: Mon, 10 Feb 2014 16:20:23 -0800	[thread overview]
Message-ID: <xmqqmwhyqz3s.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1391892097-16169-3-git-send-email-alash3@bloomberg.net> (Albert L. Lash, IV's message of "Sat, 8 Feb 2014 15:41:36 -0500")

"Albert L. Lash, IV" <albert.lash@gmail•com> writes:

> Current text claims optimization, implying the use of
> hardlinks, when this option ratchets down the level of
> efficiency. This change explains the difference made by
> using this option, namely copying instead of hardlinking,
> and why it may be useful.
>
> Signed-off-by: Albert L. Lash, IV <alash3@bloomberg•net>
> ---
>  Documentation/git-clone.txt | 11 ++++-------
>  1 file changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
> index bf3dac0..0363d00 100644
> --- a/Documentation/git-clone.txt
> +++ b/Documentation/git-clone.txt
> @@ -55,15 +55,12 @@ repository is specified as a URL, then this flag is ignored (and we
>  never use the local optimizations).  Specifying `--no-local` will
>  override the default when `/path/to/repo` is given, using the regular
>  Git transport instead.
> -+
> -To force copying instead of hardlinking (which may be desirable if you
> -are trying to make a back-up of your repository), but still avoid the
> -usual "Git aware" transport mechanism, `--no-hardlinks` can be used.
>  
>  --no-hardlinks::
> -	Optimize the cloning process from a repository on a
> -	local filesystem by copying files under `.git/objects`
> -	directory.
> +	Force the cloning process from a repository on a local
> +	filesystem to copy the files under the `.git/objects`
> +	directory instead of using hardlinks. This may be desirable
> +	if you are trying to make a back-up of your repository.

Makes sense, and it is kind of embarrassing (I have to suspect that
this was originally the description of "--hardlinks" option).

[PATCH {1,2}/4] looked trivially correct, too.

Thanks.

next prev parent reply	other threads:[~2014-02-11  0:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 20:41 [PATCH 1/4] docs/merge-strategies: remove hyphen from mis-merges Albert L. Lash, IV
2014-02-08 20:41 ` [PATCH 2/4] docs/git-remote: capitalize first word of initial blurb Albert L. Lash, IV
2014-02-08 20:41 ` [PATCH 3/4] docs/git-clone: clarify use of --no-hardlinks option Albert L. Lash, IV
2014-02-11  0:20   ` Junio C Hamano [this message]
2014-02-08 20:41 ` [PATCH 4/4] docs/git-blame: explain more clearly the example pickaxe use Albert L. Lash, IV
2014-02-11  0:21   ` Junio C Hamano
2014-02-10 21:06 ` [PATCH 1/4] docs/merge-strategies: remove hyphen from mis-merges Junio C Hamano

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=xmqqmwhyqz3s.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=alash3@bloomberg$(echo .)net \
    --cc=albert.lash@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox