On Fri, Aug 18, 2017 at 9:50 AM, Junio C Hamano <gits...@pobox.com> wrote: > I am not sure if I follow. Submodules are not trees and one of the > reasons people may want to separate things into different modules is > so that they can treat them differently. If submodules allow you > a richer set of operations than a tree that is part of a monolithic > project, is that necessarily a bad thing?
It is not a bad thing on its own, but we have to consider which additional actions are useful. Jonathan brought up the following very long term vision: Eventually the everyday git commands do not treat submodules any special than trees, even the submodules git directory may be non existent (everything is absorbed into the superproject); so it really feels like a monorepo. When you want to work on a submodule individually, you have to make a new working tree.
