From: Mateusz Loskot <mateusz@loskot.net>
To: git@vger.kernel.org
Subject: Re: [Git 2.22.0] git submodule foreach now requires quoted command?
Date: Tue, 2 Jul 2019 21:11:07 +0200 [thread overview]
Message-ID: <CABUeae_NR43F+2-n9NPKUX_h2D+4nhbFT4UAaiBYFBrB5RyP7Q@mail.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1907011433531.44@tvgsbejvaqbjf.bet>
On Mon, 1 Jul 2019 at 14:33, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> On Sat, 29 Jun 2019, Mateusz Loskot wrote:
>
> > I have a script which I have used for long time, with numerous
> > git commands and one of commands is this trivial:
> >
> > git submodule foreach --recursive git clean -ffd
> >
> > I updated to Git 2.22.0 and noticed Git started to complain:
> >
> > ```
> > $ cd /d/boost
> > $ git submodule foreach --recursive git clean -ffd
> > Entering 'libs/accumulators'
> > error: unknown switch `f'
> > usage: git submodule--helper foreach [--quiet] [--recursive] [--] <command>
> >
> > -q, --quiet Suppress output of entering each submodule command
> > --recursive Recurse into nested submodules
> >
> > fatal: run_command returned non-zero status while recursing in the
> > nested submodules of libs/accumulators
> > ```
> >
> > Apparently, I have to quote the command to avoid the error
> >
> > git submodule foreach --recursive 'git clean -ffd'
> >
> > Is this expected behaviour?
> > Could anyone help me to understand what has changed?
> > I can't find any related changes in the release notes.
>
> Probably fixed in https://github.com/gitgitgadget/git/pull/263
Johannes,
Thank you for the pointer.
It does seem related indeed.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
prev parent reply other threads:[~2019-07-02 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 19:47 [Git 2.22.0] git submodule foreach now requires quoted command? Mateusz Loskot
2019-07-01 12:34 ` Johannes Schindelin
2019-07-02 19:11 ` Mateusz Loskot [this message]
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=CABUeae_NR43F+2-n9NPKUX_h2D+4nhbFT4UAaiBYFBrB5RyP7Q@mail.gmail.com \
--to=mateusz@loskot.net \
--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).