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

Re: git fetch --all --depth

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 21, 2011, 16:36 UTC
Message-ID
<7v1uxj4ml4.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20110720223902.GA6675@camk.edu.pl>
Kacper Kornet <kornet@camk.edu.pl> writes:
Show 6 quoted lines
> I have just discovered that when I use:
>
> git fetch --all --depth=<n> 
>
> the history is not deepened. Is the any specific reason for it or is it
> a bug?

The above is not specific enough to judge if you found a bug or if it is a user error.

IIRC, --depth=<n> is not "deepen by <n>", but "make sure I have at least <n> from the updated tip(s)". The shallow-clone hack gives you quite useless (even though it may be internally consistent) semantics if you shallow-cloned way in the past and fetched with --depth after the other side added many more commits than <n>, as you cannot guess what the right value of <n> should be without actually fetching without --depth.

Previous: Kacper KornetNext: Kacper Kornet
Message 2 of 4 in “git fetch --all --depth”
  1. Kacper KornetJul 20, 2011
  2. Junio C HamanoJul 21, 2011
  3. Kacper KornetJul 21, 2011
  4. ZAK MagnusJul 21, 2011

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.