From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Jeff King <peff@peff.net>,
Jason Paller-Rzepka <jasonpr@google.com>,
Stefan Beller <sbeller@google.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Multiple fetches when unshallowing a shallow clone
Date: Sat, 05 Dec 2015 20:00:28 -0800 [thread overview]
Message-ID: <xmqqmvtons4j.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CACsJy8BSNm6=E6Mo6etv_Lvdd2kpqQ7EEMBAoP-AQraYy3xU8w@mail.gmail.com> (Duy Nguyen's message of "Sat, 5 Dec 2015 06:33:47 +0100")
Duy Nguyen <pclouds@gmail.com> writes:
> On Fri, Dec 4, 2015 at 11:45 PM, Junio C Hamano <gitster@pobox.com> wrote:
> ...
>> just like a regular fetch that auto-follows tags, where it has to
>> make a second fetch if the primary fetch fails to include everything
>> that is needed for propagating the tag for whatever reason.
>>
>> Having said that, IIRC, these days a depth limited clone is created
>> implicitly with --single-branch option, and I am not sure what the
>> right behaviour for the auto-following of tags in such a repository.
>
> I suppose followtags feature has been around long enough that we can
> simply trust that and skip the second fetch?
Hmmmm, I wonder why the code needs the backfill fetch while talking
to a server that has the include-tag capability, then?
next prev parent reply other threads:[~2015-12-06 4:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 19:35 Multiple fetches when unshallowing a shallow clone Jason Paller-Rzepka
2015-12-04 20:46 ` Stefan Beller
2015-12-04 21:27 ` Jeff King
2015-12-04 21:36 ` Stefan Beller
2015-12-04 21:38 ` Jason Paller-Rzepka
2015-12-04 21:50 ` Stefan Beller
2015-12-04 21:51 ` Jeff King
2015-12-04 22:45 ` Junio C Hamano
2015-12-05 5:33 ` Duy Nguyen
2015-12-06 4:00 ` Junio C Hamano [this message]
2015-12-06 6:37 ` Jeff King
2015-12-06 7:01 ` Jeff King
2015-12-06 10:46 ` Duy Nguyen
2015-12-07 19:57 ` Jason Paller-Rzepka
[not found] ` <CACs8u9RzUVWw2Ld1K7JeO7Eci114JEiML8bbGy96m4pZZk=FnA@mail.gmail.com>
2015-12-07 21:21 ` Duy Nguyen
2015-12-07 21:27 ` Junio C Hamano
2015-12-07 21:42 ` Jeff King
2015-12-04 21:57 ` Junio C Hamano
2015-12-04 22:10 ` Jeff King
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=xmqqmvtons4j.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jasonpr@google.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sbeller@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.