From: "Peter Kästle" <peter.kaestle@nokia.com>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: Philippe Blain <levraiphilippeblain@gmail.com>,
Git mailing list <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: BUG in fetching non-checked out submodule
Date: Thu, 3 Dec 2020 10:43:34 +0100 [thread overview]
Message-ID: <168be31c-f913-4bda-cf05-adcc07c51ec8@nokia.com> (raw)
In-Reply-To: <CAN0XMOLHM0mFvXcdiXJS_yD59rSTuyJpp9N9MLvcZ5LCC1-yZA@mail.gmail.com>
Hi Ralf,
On 03.12.20 10:38, Ralf Thielow wrote:
> Hi Peter,
>
> Am Do., 3. Dez. 2020 um 09:20 Uhr schrieb Peter Kästle
> <peter.kaestle@nokia.com>:
>>> I can see the same misbehaviour when I run
>>> $ git -c submodule.recurse=false fetch --recurse-submodules
>>> too, so I think it doesn't have necessarily something to do with
>>> the 'submodule.recursive' config, but with 'recurse submodules'
>>> in general.
>> This is interesting. There are several testcases using
>> "--recurse-submodules". Have you tried, whether any of these trigger?
>>
>
> The test suite passes.
This is what I experienced. Thus it is important to get your case into
the test suite. Could you please send us a command sequence how to
create your repository structure from scratch, so that a test case can
be created? - Of course, if you want, you can also create a test case
on your own.
--
kind regards
--peter;
next prev parent reply other threads:[~2020-12-03 9:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 15:56 BUG in fetching non-checked out submodule Ralf Thielow
2020-12-02 17:19 ` Philippe Blain
2020-12-02 23:06 ` Junio C Hamano
2020-12-03 7:54 ` Peter Kästle
2020-12-03 15:25 ` Philippe Blain
2020-12-03 15:33 ` Peter Kästle
2020-12-03 18:12 ` Junio C Hamano
2020-12-04 15:23 ` [PATCH] submodules: fix of regression on fetching of non-init subsub-repo Peter Kaestle
2020-12-04 18:06 ` Eric Sunshine
2020-12-07 8:28 ` Peter Kästle
2020-12-07 8:40 ` Eric Sunshine
2020-12-07 13:46 ` [PATCH v2] " Peter Kaestle
2020-12-07 18:42 ` Philippe Blain
2020-12-07 19:43 ` Junio C Hamano
2020-12-08 8:46 ` Peter Kästle
2020-12-07 19:56 ` Junio C Hamano
2020-12-08 14:06 ` Peter Kästle
2020-12-07 19:22 ` Junio C Hamano
2020-12-07 20:44 ` Philippe Blain
2020-12-07 21:02 ` Junio C Hamano
2020-12-07 21:10 ` Junio C Hamano
2020-12-08 14:58 ` Peter Kästle
2020-12-08 15:42 ` [PATCH v3] " Peter Kaestle
2020-12-08 15:51 ` Peter Kästle
2020-12-08 20:46 ` Junio C Hamano
2020-12-08 23:25 ` Philippe Blain
2020-12-09 9:58 ` Peter Kästle
2020-12-09 10:58 ` [PATCH v4] " Peter Kaestle
2020-12-09 14:00 ` Philippe Blain
2020-12-03 7:45 ` BUG in fetching non-checked out submodule Ralf Thielow
2020-12-03 8:20 ` Peter Kästle
2020-12-03 9:38 ` Ralf Thielow
2020-12-03 9:43 ` Peter Kästle [this message]
2020-12-03 12:30 ` Ralf Thielow
2020-12-03 15:10 ` Peter Kästle
2020-12-03 16:45 ` Ralf Thielow
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=168be31c-f913-4bda-cf05-adcc07c51ec8@nokia.com \
--to=peter.kaestle@nokia.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=levraiphilippeblain@gmail.com \
--cc=ralf.thielow@gmail.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).