git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH 1/2] SubmittingPatches: extend release-notes experiment to topic names
Date: Wed, 8 Oct 2025 17:24:33 -0400	[thread overview]
Message-ID: <aObWkRSU5TO9Yvcr@nand.local> (raw)
In-Reply-To: <xmqq8qhlf777.fsf@gitster.g>

On Wed, Oct 08, 2025 at 01:51:24PM -0700, Junio C Hamano wrote:
> "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.

> > 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

  reply	other threads:[~2025-10-08 21:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 21:39 [PATCH 0/2] SubmittingPatches: guidance for topic names and multi-series efforts Taylor Blau
2025-10-07 21:39 ` [PATCH 1/2] SubmittingPatches: extend release-notes experiment to topic names Taylor Blau
2025-10-08 16:14   ` Kristoffer Haugsbakk
2025-10-08 20:51     ` Junio C Hamano
2025-10-08 21:24       ` Taylor Blau [this message]
2025-10-08 22:03         ` Kristoffer Haugsbakk
2025-10-08 21:20     ` Taylor Blau
2025-10-08 21:58       ` Kristoffer Haugsbakk
2025-10-07 21:39 ` [PATCH 2/2] SubmittingPatches: guidance for multi-series efforts Taylor Blau
2025-10-08  0:21 ` [PATCH 0/2] SubmittingPatches: guidance for topic names and " Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aObWkRSU5TO9Yvcr@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=newren@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).