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

Re: [PATCH] docs: clarify that --depth for git-fetch works with newly initialized repos

From
Sebastian Schuberth <sschuberth@gmail.com>
Date
Jan 13, 2016, 18:24 UTC
Message-ID
<56969647.7020005@gmail.com>
In-Reply-To
<568F8244.2030309@gmail.com>
On 08.01.2016 10:32, Sebastian Schuberth wrote:
Show 9 quoted lines
> The original wording sounded as if --depth could only be used to deepen or
> shorten the history of existing repos. However, that is not the case. In a
> workflow like
>
>      $ git init
>      $ git remote add origin https://github.com/git/git.git
>      $ git fetch --depth=1
>
> The newly initialized repo is properly created as a shallow repo.
Sorry for the missing sign-off, feel free to amend that in pu:
Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
-- 
Sebastian Schuberth
Previous: Sebastian Schuberth
Message 9 of 9 in “Questions on passing --depth to git-clone vs. git-fetch”
  1. Sebastian SchuberthJan 6, 2016
  2. Duy NguyenJan 6, 2016
  3. Sebastian SchuberthJan 6, 2016
  4. docs: clarify that passing --depth to git-clone implies --single-branchSebastian Schuberth, Jan 6, 2016
  5. Junio C HamanoJan 7, 2016
  6. docs: say "commits" in the --depth option wording for git-cloneSebastian Schuberth, Jan 8, 2016
  7. Sebastian SchuberthJan 13, 2016
  8. docs: clarify that --depth for git-fetch works with newly initialized reposSebastian Schuberth, Jan 8, 2016
  9. Sebastian SchuberthJan 13, 2016

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.