From: "signal@dynax.at" <signal@dynax.at>
To: git@vger.kernel.org
Subject: making use of $sm_path @ git submodule foreach —recursive
Date: Sun, 27 Nov 2022 23:53:50 +0100 [thread overview]
Message-ID: <70ED2ECF-DAF1-4CCB-9E05-2599211F3569@dynax.at> (raw)
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 reply other threads:[~2022-11-27 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 22:53 signal [this message]
2022-11-28 12:43 ` making use of $sm_path @ git submodule foreach —recursive Ævar Arnfjörð Bjarmason
2022-11-28 14:18 ` signal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70ED2ECF-DAF1-4CCB-9E05-2599211F3569@dynax.at \
--to=signal@dynax.at \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).