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

Re: [PATCH] docs: say "commits" in the --depth option wording for git-clone

From
Sebastian Schuberth <sschuberth@gmail.com>
Date
Jan 13, 2016, 18:22 UTC
Message-ID
<569695E7.4020704@gmail.com>
In-Reply-To
<568F7EDD.9020003@gmail.com>
On 08.01.2016 10:18, Sebastian Schuberth wrote:
> It is not wrong to talk about "revisions" here, but in this context
> revisions are always commits, and that is how we already name it in the
> git-fetch docs. So align the docs by always referring to "commits".
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 SchuberthNext: Sebastian Schuberth
Message 7 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.