{"thread":{"id":"60592","subject":"[PATCH 1/1] MyFirstContribution: configure shallow threads for git format-patch","startedAt":"2023-12-07T05:46:36Z","lastAt":"2023-12-08T18:06:35Z","messageCount":2,"participants":["Stan Hu","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":1},"messages":[{"id":"485407","messageId":"e197cbd28135df5523ff5ba1688566edb831f037.1701927372.git.stanhu@gmail.com","threadId":"60592","inReplyTo":"cover.1701927372.git.stanhu@gmail.com","subject":"[PATCH 1/1] MyFirstContribution: configure shallow threads for git format-patch","fromName":"Stan Hu","fromEmail":"stanhu@gmail.com","sentAt":"2023-12-07T05:46:26Z","receivedAt":"2023-12-07T05:46:36Z","isPatch":true,"sender":{"key":"stanhu@gmail.com","avatar":"https://avatars.githubusercontent.com/u/963826?v=4"},"body":"Most users on the Git mailing list prefers to use of shallow threads,\nbut this preference was not documented. This commit adds a blurb about\nhow to configure this globally via `git config`.\n\nSigned-off-by: Stan Hu <stanhu@gmail.com>\n---\n Documentation/MyFirstContribution.txt | 11 +++++++++++\n 1 file changed, 11 insertions(+)\n\ndiff --git a/Documentation/MyFirstContribution.txt b/Documentation/MyFirstContribution.txt\nindex 7cfed60c2e..3ac7455b1d 100644\n--- a/Documentation/MyFirstContribution.txt\n+++ b/Documentation/MyFirstContribution.txt\n@@ -1004,6 +1004,17 @@ determine the right way to configure it to use your SMTP server; again, as this\n configuration can change significantly based on your system and email setup, it\n is out of scope for the context of this tutorial.\n \n+[[configure-shallow-threads]]\n+=== Configuring shallow threads for `git format-patch`\n+\n+It is common practice on the Git mailing list to use \"shallow\" threads,\n+where every mail is a reply to the first mail of the series. You can\n+configure the default threading style of `git format-patch` via:\n+\n+-----\n+$ git config format.thread shallow\n+----\n+\n [[format-patch]]\n === Preparing Initial Patchset\n \n-- \n2.42.0\n\n"},{"id":"485474","messageId":"xmqqlea436xo.fsf@gitster.g","threadId":"60592","inReplyTo":"e197cbd28135df5523ff5ba1688566edb831f037.1701927372.git.stanhu@gmail.com","subject":"Re: [PATCH 1/1] MyFirstContribution: configure shallow threads for git format-patch","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-12-08T18:06:27Z","receivedAt":"2023-12-08T18:06:35Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Stan Hu <stanhu@gmail.com> writes:\n\n> +[[configure-shallow-threads]]\n> +=== Configuring shallow threads for `git format-patch`\n> +\n> +It is common practice on the Git mailing list to use \"shallow\" threads,\n> +where every mail is a reply to the first mail of the series. You can\n> +configure the default threading style of `git format-patch` via:\n> +\n> +-----\n> +$ git config format.thread shallow\n> +----\n\n\nHmph, I do not think I have such an option defined, yet I send out\nmy series as \"shallow\" threads.  I think the new description is\nsomewhat misleading as-is.  Isn't it applicable ONLY to those who\nlet \"format-patch\" decide the message ID for patches?  If the user\nlets \"git send-email\" assign the message IDs (and hence the thread\nstructure), the configuration variable would not apply, no?\n"}]}