Jens Lehmann <Jens.Lehmann@xxxxxx> writes: > We will skip the check for submodules without remotes, does that lessen > your annoyance? We still think it is a good idea to have that test enabled > by default, but it might be a good idea to wait with that until we provide > a central config option to enable users to turn that off with a simple > "git config push.recurseSubmodules off". What do you think? I would rather see a questionable (in the sense that it can trigger false positive and annoy users of workflows you didn't anticipate) new feature turned off by default, so that interested people who _do_ want to can use it knowing what they are getting into, to find out as much unexpected fallout as possible. So if we want to give this topic early graduation, I would suggest making it a command line option that defaults to off first, then in a later commit add a configuration option to enable people to turn it on (and allow those who do not see the point of the new feature to keep it turned off permanently). Enabling the feature by default can be done in a later version after the feature proves to be truly useful for people who opted into the experiment. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html