On Tue, Oct 04, 2016 at 09:19:01AM -0700, Junio C Hamano wrote: > Jeff King <p...@peff.net> writes: > > > As I argued in [1], I think it's not just "this must be cheaper" but > > "this must not be enabled if submodules are not in use at all". Most > > repositories don't have submodules enabled at all, so anything that > > cause any extra traversal, even of a portion of the history, is going to > > be a net negative for a lot of people. > > > > I think the only sane default is going to be some kind of heuristic that > > says "submodules are probably in use". > > Why should we even have a default different from today's? If most > repositories don't have submodules enabled at all, we can just let > those working with submodules enabled to toggle their configuration > and that is an very easy to understand solution, no?
You will not see any complaint from me on that. I was taking for granted that the current default is inconvenient to submodule users, but I don't have any experience myself. -Peff
