Stefan Beller <sbel...@google.com> writes: > 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.?
