git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCHv2 2/8] Doc: shallow clone deepens _to_ new depth

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 19, 2012, 03:45 UTC
Message-ID
<7vvcfaiskf.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1348010734-664-3-git-send-email-philipoakley@iee.org>
Philip Oakley <philipoakley@iee.org> writes:
Show 18 quoted lines
> 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.
Previous: Philip Oakley
Message 2 of 2 in “[PATCHv2 2/8] Doc: shallow clone deepens _to_ new depth”
  1. Philip OakleySep 18, 2012
  2. Junio C HamanoSep 19, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.