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

making use of $sm_path @ git submodule foreach —recursive

From
Ssignal@dynax.at <signal@dynax.at>
Date
Nov 27, 2022, 22:53 UTC
Message-ID
<70ED2ECF-DAF1-4CCB-9E05-2599211F3569@dynax.at>
Hi,

when using git submodule foreach —recursive [..] $sm_path contains only the relative part of the latest recursion. Since the command has no generic way of knowing from which recursion level it is executed any $sm_path of deeper recursion level is useless unless there is a way for the command to find out from which recursion it is called.

I suggest $sm_path should be extended to be relative to the repo from where the submodule recursion started or another variable should contain the recursive part.

Viele Grüße/Cheers, Hagen.

Next: Ævar Arnfjörð Bjarmason
Message 1 of 3 in “making use of $sm_path @ git submodule foreach —recursive”
  1. signal@dynax.atNov 27, 2022
  2. Ævar Arnfjörð BjarmasonNov 28, 2022
  3. signal@dynax.atNov 28, 2022

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.