Re: BUG in fetching non-checked out submodule

["Peter Kästle" <peter.kaestle@nokia.com>]

Hi Ralf,

On 03.12.20 08:45, Ralf Thielow wrote:
> Am Mi., 2. Dez. 2020 um 18:20 Uhr schrieb Philippe Blain
> <levraiphilippeblain@gmail.com>:
>>
>> Ok, you don't add '--init' but the submodule gets checked out,
>> so it looks like you have 'submodule.active' set to a pathspec
>> that matches 'sha1collisiondetection'. Did you clone the git repo
>> with '--recurse-submodules', which would add '.' as the value of
>> 'submodule.active' ? Or maybe you manually configured that value
>> in your global gitconfig ?
> 
> Sry, I did not mention that I started with the submodule already
> initialized and checked out. IIRC I deinitialized the submodule with
> 'git submodule deinit -f sha1collisiondetection/' and ran 'git fetch'
> to see if it happens on the git repo, too, since I encountered the
> issue on another repo first.
> 
> 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?

-- 
kind regards
--peter;