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

Re: Questions on passing --depth to git-clone vs. git-fetch

From
Sebastian Schuberth <sschuberth@gmail.com>
Date
Jan 6, 2016, 13:04 UTC
Message-ID
<568D10D6.7020707@gmail.com>
In-Reply-To
<CACsJy8D5DeDOCd1tn876s3+2fBR6e-X1UANkAeiw8tzAeDcDng@mail.gmail.com>
On 1/6/2016 13:41, Duy Nguyen wrote:
> I think the culprit is the "git remote add" line. "git clone --depth"
> by default will fetch only one branch (aka --single-branch option in
> git-clone). But I suspect when you add a new remote, the default

Now that you mention it I see this being documented as part of --single-branch instead of --depth, which I think is confusing. I'll send a patch.

-- 
Sebastian Schuberth
Previous: Duy NguyenNext: Sebastian Schuberth
Message 3 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.