On Wed, Aug 17, 2016 at 2:05 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Stefan Beller <sbeller@xxxxxxxxxx> writes: > >> If working with submodules, there are more reports of missing submodules >> rather than the desire to push the superproject without the submodules >> to be pushed out. > > I do not know how you are counting the "more reports" part of that > assertion, but it is very likely that it is biased by the current > default. If you flip the default, you would see more reports that > say "I know I wasn't ready to push the submodule part out; don't bug > me". > > IOW, those who want to have something different always sound louder, > because people who are satisified tend to stay silent. Yeah I thought about this mistake and how to get real numbers, but I was just misled by some people on #git IRC waving hands. ;) > >> Flipping the default to check for submodules is safer >> than the current default of ignoring submodules while pushing. > > That part of the assertion, on the other hand, is justifiable. ok. > >> Signed-off-by: Stefan Beller <sbeller@xxxxxxxxxx> >> --- >> >> Probably too late for the 2.10 release as I'd propose to keep it in master for >> quite a while before actually doing a release with this. > > I think you meant 'next' not 'master'. We have a few "let's keep it > in 'next' to see if people scream" topics there already--the more > the merrier? ;-) Well we put it into next, but that are not as many people as those running master I would think, so I would want to maximize both times in next as well as in master, e.g. if you put it into next today (unreasonable, but let's assume), then it could make it into master next week, and then be released as part of 2.10 IIUC the release schedule. I would say that is too fast. rather I'd see this patch transition from next to master just after a release, such that it lives in master for a full release cycle before being actually in a release. So far for my line of thinking. Thanks, Stefan -- 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