{"thread":{"id":"38406","subject":"git --recurse-submodule does not recurse to sub-submodules (etc.)","startedAt":"2015-01-19T20:19:12Z","lastAt":"2015-01-23T22:02:34Z","messageCount":3,"participants":["Maximilian Held","Jens Lehmann"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"254906","messageId":"CACgLhq_kMv2cj4RHr8Yx5tnYup5enCJVMrZf9Yt9Y5-bkfozLg@mail.gmail.com","threadId":"38406","inReplyTo":null,"subject":"git --recurse-submodule does not recurse to sub-submodules (etc.)","fromName":"Maximilian Held","fromEmail":"maximilian.held83@gmail.com","sentAt":"2015-01-19T20:19:12Z","receivedAt":"2015-01-19T20:19:12Z","isPatch":false,"sender":{"key":"maximilian.held83@gmail.com","avatar":null},"body":"I have a directory with nested submodules, such as:\n\nsupermodule/submodule/sub-submodule/sub-sub-submodule\n\nWhen I cd to supermodule and do:\n\n\"git push --recurse-submodule=check\" (or on-demand),\n\ngit only pushes the submodule, but not the sub-submodule etc.\n\nMaybe this is expected behavior and not a bug, but I thought it was\npretty unintuitive. I expected that git would push, well, recursively.\n\nBest\nMax\n\nhttp://www.maxheld.de\n"},{"id":"254954","messageId":"54BEC6C7.8070103@web.de","threadId":"38406","inReplyTo":"CACgLhq_kMv2cj4RHr8Yx5tnYup5enCJVMrZf9Yt9Y5-bkfozLg@mail.gmail.com","subject":"Re: git --recurse-submodule does not recurse to sub-submodules (etc.)","fromName":"Jens Lehmann","fromEmail":"jens.lehmann@web.de","sentAt":"2015-01-20T21:21:11Z","receivedAt":"2015-01-20T21:21:11Z","isPatch":false,"sender":{"key":"jens.lehmann@web.de","avatar":"https://avatars.githubusercontent.com/u/135220?v=4"},"body":"Am 19.01.2015 um 21:19 schrieb Maximilian Held:\n> I have a directory with nested submodules, such as:\n>\n> supermodule/submodule/sub-submodule/sub-sub-submodule\n>\n> When I cd to supermodule and do:\n>\n> \"git push --recurse-submodule=check\" (or on-demand),\n>\n> git only pushes the submodule, but not the sub-submodule etc.\n>\n> Maybe this is expected behavior and not a bug, but I thought it was\n> pretty unintuitive. I expected that git would push, well, recursively.\n\nI agree this is unexpected and should be fixed. I suspect the fix\nwould be to teach the push_submodule() function to use the same\nflags that were used for the push in the superproject.\n"},{"id":"255228","messageId":"CACgLhq_V-uj1pNjKyEA8RaOtxjfNca+R0LRPp-6KgDw6NCCGpg@mail.gmail.com","threadId":"38406","inReplyTo":"54BEC6C7.8070103@web.de","subject":"Re: git --recurse-submodule does not recurse to sub-submodules (etc.)","fromName":"Maximilian Held","fromEmail":"maximilian.held83@gmail.com","sentAt":"2015-01-23T22:02:34Z","receivedAt":"2015-01-23T22:02:34Z","isPatch":false,"sender":{"key":"maximilian.held83@gmail.com","avatar":null},"body":"Thanks, Jens.\n\nIncidentally,\n\ngit submodule update --init --recursive\n\nDoes exactly what expected – it updates sub/sub/submodules, so there\nis certainly some inconsistency in how the --recursive flag is handled\nhere.\ninfo@maxheld.de | http://www.maxheld.de | http://www.civicon.de |\nMobil: +49 151 22958775 | Skype: maximilian.held\nBremen International Graduate School of Social Sciences | Wiener\nStraße / Celsiusstraße | 28359 Bremen | Germany\n\n\nOn Tue, Jan 20, 2015 at 10:21 PM, Jens Lehmann <Jens.Lehmann@web.de> wrote:\n> Am 19.01.2015 um 21:19 schrieb Maximilian Held:\n>\n>> I have a directory with nested submodules, such as:\n>>\n>> supermodule/submodule/sub-submodule/sub-sub-submodule\n>>\n>> When I cd to supermodule and do:\n>>\n>> \"git push --recurse-submodule=check\" (or on-demand),\n>>\n>> git only pushes the submodule, but not the sub-submodule etc.\n>>\n>> Maybe this is expected behavior and not a bug, but I thought it was\n>> pretty unintuitive. I expected that git would push, well, recursively.\n>\n>\n> I agree this is unexpected and should be fixed. I suspect the fix\n> would be to teach the push_submodule() function to use the same\n> flags that were used for the push in the superproject.\n"}]}