submodule update --init --recursive doesn`t work git 1.7.10

Piotr Pientka· Jun 12, 2012, 08:07 UTC · lore

When I have nested submodules, after Add new nested submodule and make "submodule update --init --recursive", I have failed while cloning nested modules. It looks like is a problem with path to .git

But when I add new submodule and make "submodule update --init" on each nested module, it works , but I must do it manually

It only happends on git 1.7.10. On git 1.7.4 it works fine.

Heiko Voigt· Jun 12, 2012, 16:49 UTC · re: Piotr Pientka · lore

Re: submodule update --init --recursive doesn`t work git 1.7.10

Hi,

On Tue, Jun 12, 2012 at 10:07:02AM +0200, Piotr Pientka wrote:

Show 9 quoted lines

> When I have nested submodules, after Add new nested submodule and make
> "submodule update --init --recursive", I have failed while cloning
> nested modules.
> It looks like is a problem with path to .git
> 
> But when I add new submodule and make "submodule update --init" on
> each nested module, it works , but I must do it manually
> 
> It only happends on git 1.7.10. On git 1.7.4 it works fine.

This description is missing some information. Might this be the same issue with relative superproject origin urls these patches

http://thread.gmane.org/gmane.comp.version-control.git/199314

are trying to address?

Could you provide a script that illustrates what you are seeing?

Cheers Heiko