From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: "Taylor Blau" <me@ttaylorr.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, 08 Oct 2025 13:51:24 -0700 [thread overview]
Message-ID: <xmqq8qhlf777.fsf@gitster.g> (raw)
In-Reply-To: <85dbe67e-f252-4548-910d-4af29939806a@app.fastmail.com> (Kristoffer Haugsbakk's message of "Wed, 08 Oct 2025 18:14:42 +0200")
"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".
> 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.
next prev parent reply other threads:[~2025-10-08 20:51 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 [this message]
2025-10-08 21:24 ` Taylor Blau
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=xmqq8qhlf777.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=me@ttaylorr.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).