Re: [PATCH] git: add --no-optional-locks option

From: Jeff King <peff@peff.net>
Date: Sep 22, 2017, 21:25 UTC
Message-ID: <20170922212525.kxldygbjrmjqu7ci@sigill.intra.peff.net>
In-Reply-To: <CAGZ79kaUTdFi5LkgR6zKeb+CH8vpfPQRZf6bFqRfYY-YXy_TNA@mail.gmail.com>

On Fri, Sep 22, 2017 at 01:09:32PM -0700, Stefan Beller wrote:

Show 12 quoted lines

> On Thu, Sep 21, 2017 at 9:25 PM, Jeff King <peff@peff.net> wrote:
> 
> >
> > But imagine that "git status" learns to recurse into submodules and run
> > "git status" inside them. Surely we would want the submodule repos to
> > also avoid taking any unnecessary locks?
> 
> You can teach Git to recurse into submodules already at home,
> just 'git config status.submoduleSummary none'. ;)
> 
> It occurs to me that the config name is badly choosen, as it stores
> an argument for git status --ignore-submodules[=mode]

Ah, thanks. I _thought_ we could already do that but when I went looking for the standard --recursive option I couldn't find it.

So yes, I would think we would want this option to apply recursively in that case, even when we cross repository boundaries.

-Peff