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

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

From
Taylor Blau <me@ttaylorr.com>
Date
Oct 8, 2025, 21:24 UTC
Message-ID
<aObWkRSU5TO9Yvcr@nand.local>
In-Reply-To
<xmqq8qhlf777.fsf@gitster.g>
On Wed, Oct 08, 2025 at 01:51:24PM -0700, Junio C Hamano wrote:
Show 16 quoted lines
> "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
>
> > I like the format in the cover letter:
> >
> >      * tb/submitting-patches
> >
> >        Extend the experimental protocol used by contributors to propose a
> >        topic branch name in addition to a description, and describe how to
> >        name multi-series efforts.
>
> Hmph, but the paragraphs that eventually go into RelNotes are not
> commit log messages.  "Extend the protocol A to achieve X" is what
> we would write in our proposed log messages, but after such a patch
> achieves X by extending the protocol A, we'd report it in our
> release notes by saying something ike "The protocol A was extended
> in such and such way to achieve X".

Fair, though I think the existing documentation suffers from the same issue. It says both:

  you can propose a one-paragraph summary that should appear in the
  "What's cooking" report
and:
  Please write a 2-5 line paragraph that will fit well in our release
  notes.

I think that's a separate issue that we should clarify as a prerequisite to the two patches proposed here.

Show 8 quoted lines
> > But it was noted[1] that the-topic-summary doesn’t seem to have been
> > used much. That’s not surprising given that the instruction makes
> > the-topic-summary blend in with the rest of the cover letter and doesn’t
> > signal that the author intends for the first paragraph to be used as
> > such. This patch shares the same problem.
>
> Oh, that's a new theory.  So you are saying that authors may have
> tried but I (and others) failed to notice?  It cetainly is possible.

Certainly possible indeed, but I am not so sure this is happening. At least from the series that I have looked at since this experiment was introduced, I have seen vanishingly few examples of contributors following the process suggested here.

Perhaps I am missing them too, but my sense is that it's likelier that contributors just simply aren't doing this rather than doing it and both of us are not noticing it.

That may be an argument for dropping this section entirely and declaring the experiment as having failed?

Thanks, Taylor

Previous: Junio C HamanoNext: Kristoffer Haugsbakk
Message 5 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.