public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Florian Schmidt <flosch@nutanix.com>
Cc: Derrick Stolee <stolee@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: Option for "git submodule foreach" to also run on the parent git?
Date: Mon, 9 Mar 2026 15:30:01 -0400	[thread overview]
Message-ID: <20260309193001.GD309867@coredump.intra.peff.net> (raw)
In-Reply-To: <66419a04-67b0-4b60-bf23-078cf92b2c04@nutanix.com>

On Mon, Mar 09, 2026 at 05:43:14PM +0000, Florian Schmidt wrote:

> > but at that
> > point, wouldn't it be simpler to explain what you are doing as
> > 
> >      do-this . ;# do it here
> >      git submodule foreach do-this ;# do it there all over
> 
> That's basically what's I'm doing. I figured instead of doing "foo && git
> submodule foreach foo", a "git submodule foreach --also-parent foo" would be
> marginally neater. But I don't feel strongly about it.

These days we also have git-for-each-repo. It is primarily about running
a command in a set of otherwise unrelated repos. But I wonder if:

  git for-each-repo --submodules do-this

would be a natural fit as an alternative to "git submodule foreach"? And
then you can imagine a "--current" option to discover the current repo
and include it in the list. And then:

  git for-each-repo --submodules --current do-this

would do what you want.

I dunno. I do not have any need for this myself, but just thinking out
loud.

-Peff

  reply	other threads:[~2026-03-09 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 12:52 Option for "git submodule foreach" to also run on the parent git? Florian Schmidt
2026-03-09 15:15 ` Junio C Hamano
2026-03-09 17:43   ` Florian Schmidt
2026-03-09 19:30     ` Jeff King [this message]
2026-03-09 21:03       ` brian m. carlson
2026-03-09 22:14 ` D. Ben Knoble

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260309193001.GD309867@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=flosch@nutanix.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=stolee@gmail.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox