{"thread":{"id":"47398","subject":"[PATCH] RelNotes/2.16: Fix submodule recursing argument","startedAt":"2017-12-07T19:51:56Z","lastAt":"2017-12-07T20:35:22Z","messageCount":2,"participants":["Stefan Beller","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"334356","messageId":"20171207195145.11965-1-sbeller@google.com","threadId":"47398","inReplyTo":null,"subject":"[PATCH] RelNotes/2.16: Fix submodule recursing argument","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2017-12-07T19:51:45Z","receivedAt":"2017-12-07T19:51:56Z","isPatch":true,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"Some commands take a plain `--recursive` flag as an indication to recurse\ninto submodules, git-clone is a notable user facing example, an internal\nexample is in builtin/submodule--helper. Other commands such as git-merge\ntake the `--recursive` flag to indicate recursing in their specific area\nof expertise.\n\nGiven these examples it is evident, that such a flag is too generic as\nwe can think of other recursive applications as well: recursing into trees\nis another example.\n\nThat is why any submodule related recursing tries to use the explicit\n`--recurse-submodules` instead. Any occurrences of the genric recurse flag\nare historic accidents.\n\nSigned-off-by: Stefan Beller <sbeller@google.com>\n---\n\nJunio, feel free to just squash this into a future update\nof the release notes.\n\nThanks,\nStefan\n\n Documentation/RelNotes/2.16.0.txt | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/RelNotes/2.16.0.txt b/Documentation/RelNotes/2.16.0.txt\nindex 431bd5e34a..8fbc233e56 100644\n--- a/Documentation/RelNotes/2.16.0.txt\n+++ b/Documentation/RelNotes/2.16.0.txt\n@@ -275,7 +275,7 @@ Fixes since v2.15\n    ask the underlying \"git fetch\" to go over IPv4/IPv6, which has been\n    corrected.\n \n- * \"git checkout --recursive\" may overwrite and rewind the history of\n+ * \"git checkout --recurse-submodules\" may overwrite and rewind the history of\n    the branch that happens to be checked out in submodule\n    repositories, which might not be desirable.  Detach the HEAD but\n    still allow the recursive checkout to succeed in such a case.\n-- \n2.15.1.424.g9478a66081-goog\n\n"},{"id":"334363","messageId":"xmqqpo7qcm4c.fsf@gitster.mtv.corp.google.com","threadId":"47398","inReplyTo":"20171207195145.11965-1-sbeller@google.com","subject":"Re: [PATCH] RelNotes/2.16: Fix submodule recursing argument","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-12-07T20:35:15Z","receivedAt":"2017-12-07T20:35:22Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Stefan Beller <sbeller@google.com> writes:\n\n> Junio, feel free to just squash this into a future update\n> of the release notes.\n> ...\n> - * \"git checkout --recursive\" may overwrite and rewind the history of\n> + * \"git checkout --recurse-submodules\" may overwrite and rewind the history of\n\nThanks.\n"}]}