git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: gitList <git@vger.kernel.org>
Subject: Re: [PATCHv2 2/8] Doc: shallow clone deepens _to_ new depth
Date: Tue, 18 Sep 2012 20:45:36 -0700	[thread overview]
Message-ID: <7vvcfaiskf.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1348010734-664-3-git-send-email-philipoakley@iee.org> (Philip Oakley's message of "Wed, 19 Sep 2012 00:25:28 +0100")

Philip Oakley <philipoakley@iee.org> writes:

> Clarify that 'depth=' specifies the new depth from the remote's
> branch tip. It does not add the depth to the existing shallow clone.
> (details from pack-protocol.txt).
> Clarify that tags are not fetched. (details from shallow.txt)
>
> Signed-off-by: Philip Oakley <philipoakley@iee.org>
>
> diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt
> index 39d326a..b4d6476 100644
> --- a/Documentation/fetch-options.txt
> +++ b/Documentation/fetch-options.txt
> @@ -10,7 +10,8 @@
>  --depth=<depth>::
>  	Deepen the history of a 'shallow' repository created by
>  	`git clone` with `--depth=<depth>` option (see linkgit:git-clone[1])
> -	by the specified number of commits.
> +	to the specified number of commits from the tip of each remote
> +	branch history. Tags for the deepened commits are not fetched.

Looks good; thanks.

      reply	other threads:[~2012-09-19  3:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 23:25 [PATCHv2 2/8] Doc: shallow clone deepens _to_ new depth Philip Oakley
2012-09-19  3:45 ` Junio C Hamano [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=7vvcfaiskf.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=philipoakley@iee.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 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).