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

Re: [PATCH] Don't do status in submodules if status.SubmoduleSummary unset

From
Alex Riesen <raa.lkml@gmail.com>
Date
May 20, 2010, 19:34 UTC
Message-ID
<AANLkTikQDEwA7Iih9hniYzLfSGnPvZ9PTDNtSKfJPa9d@mail.gmail.com>
In-Reply-To
<4BF57538.5040204@web.de>
On Thu, May 20, 2010 at 19:45, Jens Lehmann <Jens.Lehmann@web.de> wrote:
Show 6 quoted lines
> Am 20.05.2010 16:12, schrieb Alex Riesen:
>> Maybe because we do a (kind of) gentle status run on submodules
>> whether the status.SubmoduleSummary set or not.
>
> Yup, because checking a submodule for its dirtiness has to be done
> no matter if the summary output is also wanted.
Yeah. Why?
Show 8 quoted lines
>> Usually a background
>> run of "git status" for every submodules goes unnoticed, just
>> sometimes a submodule is a little too big.
>>
>> I tried this, but feels like a bit of overkill.
>
> This patch seems to disable submodule output completely for the default
> case (when status.SubmoduleSummary is false) and breaks 17 test cases.
That's why I said it feels like overkill
Previous: Jens LehmannNext: Jens Lehmann
Message 3 of 4 in “Don't do status in submodules if status.SubmoduleSummary unset”
  1. Don't do status in submodules if status.SubmoduleSummary unsetAlex Riesen, May 20, 2010
  2. Jens LehmannMay 20, 2010
  3. Alex RiesenMay 20, 2010
  4. Jens LehmannMay 20, 2010

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.