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

Re: [RFC PATCH] change default for status.submoduleSummary to true

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 30, 2017, 06:04 UTC
Message-ID
<xmqqmvc37120.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170330012025.22122-1-sbeller@google.com>
Stefan Beller <sbeller@google.com> writes:
Show 11 quoted lines
> A user complained about the workflow with submodules:
>> Re submodules pain, I've seen a lot of people get confused about
>> how and when to commit submodule changes. The main thing missing
>> in the related UIs is some way to summarize the subproject commit
>> diff in a human readable way. Maybe last log message would be better
>> than just sha?
>
> We could advise all the confused users to turn on
> status.submoduleSummary.  However there is no downside from turning
> it on by default apart from a slight change in behavior and bit
> longer output of git-status and the help in git-commit.

Is "there is no downside" substantiated or just hand-waving? Any pros-and-cons analysis, e.g. performance implications, etc.?

Previous: Jacob KellerNext: Stefan Beller
Message 3 of 4 in “change default for status.submoduleSummary to true”
  1. change default for status.submoduleSummary to trueStefan Beller, Mar 30, 2017
  2. Jacob KellerMar 30, 2017
  3. Junio C HamanoMar 30, 2017
  4. Stefan BellerMar 30, 2017

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.