{"thread":{"id":"32021","subject":"why '--init' in git-submodule update","startedAt":"2012-11-05T16:30:51Z","lastAt":"2012-11-07T07:10:45Z","messageCount":3,"participants":["Francis Moreau","Heiko Voigt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"202558","messageId":"CAC9WiBgpHWFGW-z5fnQR_EWnfGJUw+G3b7C6tYMGuVu1S-kP9A@mail.gmail.com","threadId":"32021","inReplyTo":null,"subject":"why '--init' in git-submodule update","fromName":"Francis Moreau","fromEmail":"francis.moro@gmail.com","sentAt":"2012-11-05T16:30:51Z","receivedAt":"2012-11-05T16:30:51Z","isPatch":false,"sender":{"key":"francis.moro@gmail.com","avatar":null},"body":"Hello,\n\nI'm wondering why the --init option from git-submodule-update is not\nat least the defaut. Or even wilder, why this option exists at all and\ngit-submodule-update always behave like --init was always passed.\n\nThanks\n--\nFrancis\n"},{"id":"202566","messageId":"20121105213004.GA2797@book.hvoigt.net","threadId":"32021","inReplyTo":"CAC9WiBgpHWFGW-z5fnQR_EWnfGJUw+G3b7C6tYMGuVu1S-kP9A@mail.gmail.com","subject":"Re: why '--init' in git-submodule update","fromName":"Heiko Voigt","fromEmail":"hvoigt@hvoigt.net","sentAt":"2012-11-05T21:30:09Z","receivedAt":"2012-11-05T21:30:09Z","isPatch":false,"sender":{"key":"hvoigt@hvoigt.net","avatar":"https://avatars.githubusercontent.com/u/184958?v=4"},"body":"Hi,\n\nOn Mon, Nov 05, 2012 at 05:30:51PM +0100, Francis Moreau wrote:\n> I'm wondering why the --init option from git-submodule-update is not\n> at least the defaut. Or even wilder, why this option exists at all and\n> git-submodule-update always behave like --init was always passed.\n\nThat was a design decision. People may not be interested in all\nsubmodules but just a subset they are working with. E.g. think of a\nlarge media directory as a submodule the developers might not be\ninterested in having it around all the time because only the designers\nare heavily working with it.\n\nSo the rationale is that you should ask for a certain submodule to be\ninitialized to get it. If there is demand for it we could of course think\nabout offering a config option in .gitmodules to allow enabling it by\ndefault for some submodules.\n\nCheers Heiko\n"},{"id":"202610","messageId":"CAC9WiBhvEX8VCprytK8HMTdFX+iQE7K=a4cKb8MphhpDowaw6A@mail.gmail.com","threadId":"32021","inReplyTo":"20121105213004.GA2797@book.hvoigt.net","subject":"Re: why '--init' in git-submodule update","fromName":"Francis Moreau","fromEmail":"francis.moro@gmail.com","sentAt":"2012-11-07T07:10:45Z","receivedAt":"2012-11-07T07:10:45Z","isPatch":false,"sender":{"key":"francis.moro@gmail.com","avatar":null},"body":"Hi,\n\nOn Mon, Nov 5, 2012 at 10:30 PM, Heiko Voigt <hvoigt@hvoigt.net> wrote:\n> Hi,\n>\n> On Mon, Nov 05, 2012 at 05:30:51PM +0100, Francis Moreau wrote:\n>> I'm wondering why the --init option from git-submodule-update is not\n>> at least the defaut. Or even wilder, why this option exists at all and\n>> git-submodule-update always behave like --init was always passed.\n>\n> That was a design decision. People may not be interested in all\n> submodules but just a subset they are working with. E.g. think of a\n> large media directory as a submodule the developers might not be\n> interested in having it around all the time because only the designers\n> are heavily working with it.\n>\n\nThanks for explaining.\n\nAnother possible solution was to check if one or several submodules\nare already checkout. If so then update only them. If none of them is\ncheckout then assume --init is passed and init all of them. Same if a\npath is passed and this path corresponds to a submodule not checkout\nyet.\n\n--\nFrancis\n"}]}