{"thread":{"id":"53800","subject":"Feature Request: Add 'active' configuration to .gitmodules","startedAt":"2020-07-06T10:20:15Z","lastAt":"2020-07-06T10:20:15Z","messageCount":1,"participants":["4dr14n31t0r Th3 G4m3r"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"401040","messageId":"CAOKK28C4-3-+rxcggYdYuzuxNqdstA8BfJtY63KkHF=iZ+soxg@mail.gmail.com","threadId":"53800","inReplyTo":null,"subject":"Feature Request: Add 'active' configuration to .gitmodules","fromName":"4dr14n31t0r Th3 G4m3r","fromEmail":"4dr14n31t0r@gmail.com","sentAt":"2020-07-06T10:19:54Z","receivedAt":"2020-07-06T10:20:15Z","isPatch":false,"sender":{"key":"4dr14n31t0r@gmail.com","avatar":null},"body":"There are cases in which reading the 'active' config from the\n.gitmodules file can be useful. For instance, if you are working in a\nfeature branch in the superproject and that feature requires some\nsubmodules to be active, it is redundant to each time any new\ndeveloper that checks out this feature branch to also mark as active\nthese submodules. This way, when you record the contents of the\nsuperproject in a commit you can also record which submodules where\nactive at the moment.\n\nYou can have git reading first the active config from .git/config, and\nif that configuration is not present use the one in .gitmodules to\nallow compatibility with older versions of git.\n\nIf you read the url configuration from the .gitmodules file the same\nway, you wouldn't have to initialize each time the submodules.\n"}]}