git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Heiko Voigt <hvoigt@hvoigt.net>
Date
Jun 12, 2012, 16:49 UTC
Message-ID
<20120612164933.GA15093@book.hvoigt.net>
In-Reply-To
<CAMgq-fJN=-XnHOZyAUbQ4uiQ61Ryzn-4d69QBtUJeXAxNvSBiw@mail.gmail.com>
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
Previous: Piotr Pientka
Message 2 of 2 in “submodule update --init --recursive doesn`t work git 1.7.10”
  1. Piotr PientkaJun 12, 2012
  2. Heiko VoigtJun 12, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.