Re: BUG in fetching non-checked out submodule

From: Ralf Thielow <ralf.thielow@gmail.com>
Date: Dec 3, 2020, 07:45 UTC
Message-ID: <CAN0XMOKEG9HLuzf9ZRXyUs_uHTXagyCdghtP98rLVoPj_75UYQ@mail.gmail.com>
In-Reply-To: <CC0FA973-E37A-4BD3-B5A2-1436DD8DF16F@gmail.com>

Hi Philippe,

Am Mi., 2. Dez. 2020 um 18:20 Uhr schrieb Philippe Blain <levraiphilippeblain@gmail.com>:

Show 7 quoted lines

>
> 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.

Ralf