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

git submodule sync --recursive

From
Phil Hord <phil.hord@gmail.com>
Date
Oct 16, 2012, 23:20 UTC
Message-ID
<CABURp0obPcS=KZJ4xaVouHBS_O+OuWGYxYwSU9wwnQrL5Huwzg@mail.gmail.com>
I noticed that this is not supported:
    git submodule sync --recursive

I do not see any discussion in the relevant commits about why it cannot or should not be supported. Is it just an itch no one has scratched?

Phil
Next: Jens Lehmann
Message 1 of 12 in “git submodule sync --recursive”
  1. Phil HordOct 16, 2012
  2. Jens LehmannOct 17, 2012
  3. Phil HordOct 23, 2012
  4. 1/2 Teach --recursive to submodule syncPhil Hord, Oct 23, 2012
  5. Jens LehmannOct 25, 2012
  6. Phil HordOct 26, 2012
  7. Phil HordOct 26, 2012
  8. Jens LehmannOct 26, 2012
  9. 0/2 Reroll submodule sync --recursivePhil Hord, Oct 26, 2012
  10. 1/2 Teach --recursive to submodule syncPhil Hord, Oct 26, 2012
  11. 2/2 Add tests for submodule sync --recursivePhil Hord, Oct 26, 2012
  12. 2/2 Add tests for submodule sync --recursivePhil Hord, Oct 23, 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.