@matheusbsbs / matheus-bagliano / commits / 16b2924aab

MyFirstContribution: recommend shallow threading of cover letters

The "MyFirstContribution" document recommends the use of deep threading of cover letters: every cover letter of subsequent iterations shall be linked to the cover letter of the preceding version. The result of this is that eventually, threads with many versions are getting nested so deep that it becomes hard to follow. Adapt the recommendation to instead propose shallow threading of cover letters: instead of linking the cover letter to the previous cover letter, the user is supposed to always link it to the first cover letter. This still makes it easy to follow the iterations, but has the benefit of nesting to a much shallower level. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Patrick Steinhardt committed Jun 15, 2026 at 14:59 UTC 16b2924aab52141bedd6612dfad16280181321c7

1 file changed +4 -4

Documentation/MyFirstContribution.adoc

+4 -4

@@ -790,7 +790,7 @@ We can note a few things:

790 v3", etc. in place of "PATCH". For example, "[PATCH v2 1/3]" would be the first of

791 three patches in the second iteration. Each iteration is sent with a new cover

792 letter (like "[PATCH v2 0/3]" above), itself a reply to the cover letter of the

793 - previous iteration (more on that below).

793 + first iteration (more on that below).

794

795 NOTE: A single-patch topic is sent with "[PATCH]", "[PATCH v2]", etc. without

796 _i_/_n_ numbering (in the above thread overview, no single-patch topic appears,

@@ -1214,7 +1214,7 @@ between your last version and now, if it's something significant. You do not

1214 need the exact same body in your second cover letter; focus on explaining to

1215 reviewers the changes you've made that may not be as visible.

1216

1217 -You will also need to go and find the Message-ID of your previous cover letter.

1217 +You will also need to go and find the Message-ID of your first cover letter.

1218 You can either note it when you send the first series, from the output of `git

1219 send-email`, or you can look it up on the

1220 https://lore.kernel.org/git[mailing list]. Find your cover letter in the

@@ -1227,8 +1227,8 @@ Message-ID: <foo.12345.author@example.com>

1227

1228 Your Message-ID is `<foo.12345.author@example.com>`. This example will be used

1229 below as well; make sure to replace it with the correct Message-ID for your

1230 -**previous cover letter** - that is, if you're sending v2, use the Message-ID

1231 -from v1; if you're sending v3, use the Message-ID from v2.

1230 +**first cover letter** - that is, for any subsequent version that you send,

1231 +always use the Message-ID from v1.

1232

1233 While you're looking at the email, you should also note who is CC'd, as it's

1234 common practice in the mailing list to keep all CCs on a thread. You can add