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

[PATCH 1/2] SubmittingPatches: extend release-notes experiment to topic names

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

In d255105c99 (SubmittingPatches: release-notes entry experiment, 2024-03-25), we began an experiment to have contributors suggest a topic description to appear in our RelNotes and "What's cooking?" reports. Extend that experiment to also welcome suggested topic branch names in addition to descriptions.

Suggested-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Taylor Blau <me@ttaylorr.com>
---
 Documentation/SubmittingPatches | 21 +++++++++++++--------
 1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 86ca7f6a78a..f48688e3700 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -579,14 +579,19 @@ line via `git format-patch --notes`.
 [[the-topic-summary]]
 *This is EXPERIMENTAL*.
 
-When sending a topic, you can propose a one-paragraph summary that
-should appear in the "What's cooking" report when it is picked up to
-explain the topic.  If you choose to do so, please write a 2-5 line
-paragraph that will fit well in our release notes (see many bulleted
-entries in the Documentation/RelNotes/* files for examples), and make
-it the first paragraph of the cover letter.  For a single-patch
-series, use the space between the three-dash line and the diffstat, as
-described earlier.
+When sending a topic, you can optionally propose a topic name and/or a
+one-paragraph summary that should appear in the "What's cooking"
+report when it is picked up to explain the topic.  If you choose to do
+so, please write a 2-5 line paragraph that will fit well in our
+release notes (see many bulleted entries in the
+Documentation/RelNotes/* files for examples), and make it the first
+(or second, if including a suggested topic name) paragraph of the
+cover letter.  If suggesting a topic name, use the format
+"XX/your-topic-name", where "XX" is a stand-in for the primary
+author's initials, and "your-topic-name" is a brief, dash-delimited
+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.
 
 [[attachment]]
 Do not attach the patch as a MIME attachment, compressed or not.
-- 
2.51.0.435.gf7a65e208c7
Previous: Taylor BlauNext: Kristoffer Haugsbakk
Message 2 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.