git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/2] SubmittingPatches: guidance for multi-series efforts

From
Taylor Blau <me@ttaylorr.com>
Date
Oct 7, 2025, 21:39 UTC
Message-ID
<f7a65e208c72e12fd71d5f788e372184250dcf3f.1759873165.git.me@ttaylorr.com>
In-Reply-To
<cover.1759873165.git.me@ttaylorr.com>

Occasionally there are efforts to contribute to the Git project that span more than one patch series in order to achieve a broader goal. By convention, the maintainer has typically suffixed the topic names with "-part-one", or "-part-1" and so on.

Document that convention and suggest some guidance on how to structure proposed topic names for multi-series efforts.

Suggested-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Taylor Blau <me@ttaylorr.com>
---
 Documentation/SubmittingPatches | 8 ++++++++
 1 file changed, 8 insertions(+)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index f48688e3700..d620bd93bd9 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -593,6 +593,14 @@ description of what your topic does.  For a single-patch series, use
 the space between the three-dash line and the diffstat, as described
 earlier.
 
+[[multi-series-efforts]]
+If your patch series is part of a larger effort spanning multiple
+patch series, briefly describe the broader goal, and state where the
+current series fits into that goal.  If you are suggesting a topic
+name as in <<the-topic-summary, section above>>, consider
+"XX/the-broader-goal-part-one", "XX/the-broader-goal-part-two", and so
+on.
+
 [[attachment]]
 Do not attach the patch as a MIME attachment, compressed or not.
 Do not let your e-mail client send quoted-printable.  Do not let
-- 
2.51.0.435.gf7a65e208c7
Previous: Kristoffer HaugsbakkNext: Junio C Hamano
Message 9 of 10 in “SubmittingPatches: guidance for topic names and multi-series efforts”
  1. 0/2 SubmittingPatches: guidance for topic names and multi-series effortsTaylor Blau, Oct 7, 2025
  2. 1/2 SubmittingPatches: extend release-notes experiment to topic namesTaylor Blau, Oct 7, 2025
  3. Kristoffer HaugsbakkOct 8, 2025
  4. Junio C HamanoOct 8, 2025
  5. Taylor BlauOct 8, 2025
  6. Kristoffer HaugsbakkOct 8, 2025
  7. Taylor BlauOct 8, 2025
  8. Kristoffer HaugsbakkOct 8, 2025
  9. 2/2 SubmittingPatches: guidance for multi-series effortsTaylor Blau, Oct 7, 2025
  10. Junio C HamanoOct 8, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.