Jon Loeliger <j...@jdl.com> writes: > So, like, Junio C Hamano said: >> Stefan Beller <sbel...@google.com> writes: >> >> > Do we want to invent a special value for url.*.insteadOf to mean >> > "look up in superproject, so I don't have to keep >> > a copy that may get stale" ? >> >> My gut feeling is that we should do the selective/filtered include >> Peff mentioned when a repository is known to be used as a submodule >> of somebody else. > > Does the management of these submodue-related config values > become easier if, instead of placing them in .config, we > place them in a git/.context file?
Do you mean that Git users that use submodules adopt a convention where a separate file in $GIT_DIR of the toplevel superproject holds pieces of configuration that are meant to be shared between the superproject and across all its submodules, and the $GIT_DIR/config file in submodules and the superproject all include that shared one via include.path mechanism? That may allow us to do without being responsible for sifting of configuration variables into safe and unsafe bins. I dunno.