From: Junio C Hamano <gitster@pobox.com>
To: Kacper Kornet <kornet@camk.edu.pl>
Cc: Alex Neronskiy <zakmagnus@google.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git fetch --all --depth
Date: Thu, 21 Jul 2011 09:36:55 -0700 [thread overview]
Message-ID: <7v1uxj4ml4.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20110720223902.GA6675@camk.edu.pl> (Kacper Kornet's message of "Thu, 21 Jul 2011 00:39:02 +0200")
Kacper Kornet <kornet@camk.edu.pl> writes:
> 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.
next prev parent reply other threads:[~2011-07-21 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 22:39 git fetch --all --depth Kacper Kornet
2011-07-21 16:36 ` Junio C Hamano [this message]
2011-07-21 20:04 ` Kacper Kornet
2011-07-21 20:40 ` ZAK Magnus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v1uxj4ml4.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kornet@camk.edu.pl \
--cc=zakmagnus@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).