* [PATCH 1/1] MyFirstContribution: configure shallow threads for git format-patch [not found] <cover.1701927372.git.stanhu@gmail.com> @ 2023-12-07 5:46 ` Stan Hu 2023-12-08 18:06 ` Junio C Hamano 0 siblings, 1 reply; 2+ messages in thread From: Stan Hu @ 2023-12-07 5:46 UTC (permalink / raw) To: git; +Cc: Patrick Steinhardt, Stan Hu 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 <stanhu@gmail•com> --- Documentation/MyFirstContribution.txt | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/Documentation/MyFirstContribution.txt b/Documentation/MyFirstContribution.txt index 7cfed60c2e..3ac7455b1d 100644 --- a/Documentation/MyFirstContribution.txt +++ b/Documentation/MyFirstContribution.txt @@ -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 -- 2.42.0 ^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH 1/1] MyFirstContribution: configure shallow threads for git format-patch 2023-12-07 5:46 ` [PATCH 1/1] MyFirstContribution: configure shallow threads for git format-patch Stan Hu @ 2023-12-08 18:06 ` Junio C Hamano 0 siblings, 0 replies; 2+ messages in thread From: Junio C Hamano @ 2023-12-08 18:06 UTC (permalink / raw) To: Stan Hu; +Cc: git, Patrick Steinhardt Stan Hu <stanhu@gmail•com> writes: > +[[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 > +---- 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? ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-12-08 18:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <cover.1701927372.git.stanhu@gmail.com>
2023-12-07 5:46 ` [PATCH 1/1] MyFirstContribution: configure shallow threads for git format-patch Stan Hu
2023-12-08 18:06 ` Junio C Hamano
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox