Re: [PATCH] Re: Bug with "git submodule update" + subrepo with differing path/name?

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 19, 2017, 22:19 UTC
Message-ID: <xmqqk1xitl6l.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20171219180230.254881-1-sbeller@google.com>

Stefan Beller <sbeller@google.com> writes:

> I tried reproducing the issue (based on the `next` branch, not 2.15,
> but I do not recall any changes in the submodule area lately), and
> could not come up with a reproduction recipe,...

I do not offhand recall anything; the closest I can think of is the three-patch series <20171016135623.GA12756@book.hvoigt.net> that taught the on-demand recursive fetch to pay attention to the location in the superproject tree a submodule is bound to.

    4b4acedd61 submodule: simplify decision tree whether to or not to fetch
    c68f837576 implement fetching of moved submodules
    01ce12252c fetch: add test to make sure we stay backwards compatible

But IIRC, "submodule update" uses a separate codepath?