Junio C Hamano <gitster@xxxxxxxxx> writes: > I haven't reverted the merge of that "submodule update" topic yet; I > should do that soonish. > ... Sigh... This is giving me a lot of headache. As 23d25e48 (submodule: explicit local branch creation in module_clone, 2014-01-26) has been in 'master' since fairly early during this cycle, a lot of topics that are not planned to be on the 'maint' branch has forked from the tip of 'master' and are now contaminated by that commit. I think I have a preparatory patch to correctly revert 00d4ff1a (Merge branch 'wt/doc-submodule-name-path-confusion-2', 2014-03-31) and 06c27689 (Merge branch 'wk/submodule-on-branch', 2014-02-27), and also a part of 384364b (Start preparing for Git 2.0, 2014-03-07), but I am not sure what to do with them ;-<)) Anyhow... -- 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