{"thread":{"id":"44202","subject":"Autoupdate / autoinit submodules?","startedAt":"2016-10-03T10:00:55Z","lastAt":"2016-10-03T10:00:55Z","messageCount":1,"participants":["Jeremy Morton"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"303076","messageId":"57F229D5.6060005@game-point.net","threadId":"44202","inReplyTo":null,"subject":"Autoupdate / autoinit submodules?","fromName":"Jeremy Morton","fromEmail":"admin@game-point.net","sentAt":"2016-10-03T09:50:13Z","receivedAt":"2016-10-03T10:00:55Z","isPatch":false,"sender":{"key":"admin@game-point.net","avatar":null},"body":"Apologies if this has already been discussed, but did any of the \nproposed patches to allow .gitmodules to be configured for a submodule \nto be automatically recursive cloned and/or automatically updated on \npull make it in yet?\n\nMy use-case for submodules - which is shared libraries - almost always \nrequires a recursive clone, so having to remember the --recursive \nparam (or to use an alias) is annoying (and I usually forget), and it \nusually requires pulling the latest master on a \"git pull\", too.  I \nthink both of these things should be able to be automated through git \nmodule configuration.\n\n-- \nBest regards,\nJeremy Morton (Jez)\n"}]}