Skip to contentSkip to conversation

MyFirstContribution: configure shallow threads for git format-patch

PATCH In review Stan Hu 2 participants 2 messages Dec 7, 2023 – Dec 8, 2023 1 message not in the archive Documentation

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Stan Hu

author
#1 lore raw

PATCH 1/1 MyFirstContribution: configure shallow threads for git format-patch

Most users on the Git mailing list prefers to use of shallow threads, but this preference was not documented. This commit adds a blurb about how to configure this globally via git config.

Signed-off-by Stan Hu <[email protected]>
---
 Documentation/MyFirstContribution.txt | 11 +++++++++++
 1 file changed, 11 insertions(+)
Documentation/MyFirstContribution.txt +11 -0
index 7cfed60c2e..3ac7455b1d 100644
@@ -1004,6 +1004,17 @@ determine the right way to configure it to use your SMTP server; again, as this
 configuration can change significantly based on your system and email setup, it
 is out of scope for the context of this tutorial.
 
+[[configure-shallow-threads]]
+=== Configuring shallow threads for `git format-patch`
+
+It is common practice on the Git mailing list to use "shallow" threads,
+where every mail is a reply to the first mail of the series. You can
+configure the default threading style of `git format-patch` via:
+
+-----
+$ git config format.thread shallow
+----
+
 [[format-patch]]
 === Preparing Initial Patchset
Signature · 1 line
2.42.0
#2 lore raw

Documentation/MyFirstContribution.txt determine the right way to configure it to use your SMTP server; again, as this · line 1016

Quoted 10 lines · Stan Hu

+[[configure-shallow-threads]]
+=== Configuring shallow threads for git format-patch

Documentation/MyFirstContribution.txt +8 -0
+
+It is common practice on the Git mailing list to use "shallow" threads,
+where every mail is a reply to the first mail of the series. You can
+configure the default threading style of `git format-patch` via:
+
+-----
+$ git config format.thread shallow
+----

Hmph, I do not think I have such an option defined, yet I send out my series as "shallow" threads. I think the new description is somewhat misleading as-is. Isn't it applicable ONLY to those who let "format-patch" decide the message ID for patches? If the user lets "git send-email" assign the message IDs (and hence the thread structure), the configuration variable would not apply, no?