From: Dragan Simic <dsimic@manjaro.org>
To: Brian Lyles <brianmlyles@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, phillip.wood123@gmail.com,
"Jean-Noël AVILA" <jn.avila@free.fr>
Subject: Re: What's cooking in git.git (Mar 2024, #05; Tue, 19)
Date: Fri, 22 Mar 2024 06:14:37 +0100 [thread overview]
Message-ID: <c62a14c7de6ff487b1f66f149d685126@manjaro.org> (raw)
In-Reply-To: <17bef643ca4eabab.70b1dd9aae081c6e.203dcd72f6563036@zivdesk>
On 2024-03-22 03:47, Brian Lyles wrote:
> I would agree that it would be hard to advertise without some change
> there. I think that documenting an optional opportunity for now before
> considering if it should be a requirement later makes sense.
IMHO, making it a strict requirement would only raise the bar for
contributors even higher, and increase the "do this, do that" kind
of traffic on the mailing list. In other words, I think it's the
best to start slowly and see how many new patches will include the
additional summary.
> Would it be beneficial to request some specific heading, phrase, or
> other structured text such that this summary is obvious, or even easily
> extracted with some sort of script? Or is that perhaps overkill for
> now?
> I could see relying on any sort of automatic extraction being
> unreliable
> even with such a recommendation so perhaps it's not worth pursuing for
> that reason, but I could imagine it may be useful to have a
> standardized
> way to separate this release notes/what's cooking summary from the rest
> of the cover letter (which also acts as a summary of the series).
Of course, it would be nice to have a strict format in place, to
allow automated parsing and extraction, but I'm not sure how many
patches would actually adhere to that requirement.
next prev parent reply other threads:[~2024-03-22 5:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 16:53 What's cooking in git.git (Mar 2024, #05; Tue, 19) Junio C Hamano
2024-03-20 15:15 ` Brian Lyles
2024-03-20 16:11 ` Junio C Hamano
2024-03-21 1:13 ` Brian Lyles
2024-03-21 1:36 ` Junio C Hamano
2024-03-21 2:04 ` Brian Lyles
2024-03-21 13:02 ` Junio C Hamano
2024-03-22 1:22 ` Brian Lyles
2024-03-22 1:59 ` Junio C Hamano
2024-03-22 2:47 ` Brian Lyles
2024-03-22 5:14 ` Dragan Simic [this message]
2024-03-22 12:39 ` Max Gautier
2024-03-22 13:25 ` Dragan Simic
2024-03-22 14:46 ` Junio C Hamano
2024-03-22 5:05 ` Dragan Simic
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c62a14c7de6ff487b1f66f149d685126@manjaro.org \
--to=dsimic@manjaro.org \
--cc=brianmlyles@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jn.avila@free.fr \
--cc=phillip.wood123@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).