Thanks, Jens. Incidentally,
git submodule update --init --recursive Does exactly what expected – it updates sub/sub/submodules, so there is certainly some inconsistency in how the --recursive flag is handled here. i...@maxheld.de | http://www.maxheld.de | http://www.civicon.de | Mobil: +49 151 22958775 | Skype: maximilian.held Bremen International Graduate School of Social Sciences | Wiener Straße / Celsiusstraße | 28359 Bremen | Germany On Tue, Jan 20, 2015 at 10:21 PM, Jens Lehmann <jens.lehm...@web.de> wrote: > Am 19.01.2015 um 21:19 schrieb Maximilian Held: > >> I have a directory with nested submodules, such as: >> >> supermodule/submodule/sub-submodule/sub-sub-submodule >> >> When I cd to supermodule and do: >> >> "git push --recurse-submodule=check" (or on-demand), >> >> git only pushes the submodule, but not the sub-submodule etc. >> >> Maybe this is expected behavior and not a bug, but I thought it was >> pretty unintuitive. I expected that git would push, well, recursively. > > > I agree this is unexpected and should be fixed. I suspect the fix > would be to teach the push_submodule() function to use the same > flags that were used for the push in the superproject. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
