On Thu, May 20, 2010 at 19:45, Jens Lehmann <Jens.Lehmann@xxxxxx> wrote: > 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? >> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html