On Tue, Aug 23, 2016 at 11:38 AM, Leandro Lucarella <leandro.lucare...@sociomantic.com> wrote: > On Tue, 23 Aug 2016 20:34:46 +0200 > Leandro Lucarella <leandro.lucare...@sociomantic.com> wrote: >> This even happens after doing a: >> >> git submodule deinit <module> >> rm -fr <module> >> rm -fr .git/modules/<module> >> git submodule update --init > > One more thing, doing a clean new clone seems to work, but I have this > issue in many many repos, which are old clones, from before Git had the > ability to check for submodules. Could it be some incompatibility in > old clones with this? Is there anything I can look for in the .git/ > directory or elsewhere to fix them?
Check if push.recurseSubmodules is set? > > Thanks again! > > -- > Leandro Lucarella > Technical Development Lead > Sociomantic Labs GmbH <http://www.sociomantic.com> > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
