From: Thorsten Leemhuis <linux@leemhuis.info>
To: Karel Balej <balejk@matfyz.cz>, Jonathan Corbet <corbet@lwn.net>,
regressions@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too
Date: Mon, 1 Apr 2024 10:38:52 +0200 [thread overview]
Message-ID: <dfa22ac1-36e9-48da-a2a8-8d7818c09187@leemhuis.info> (raw)
In-Reply-To: <20240328194342.11760-3-balejk@matfyz.cz>
On 28.03.24 20:29, Karel Balej wrote:
> The regressions handling manual claims that regzbot associates patches
> fixing an issue with the report based on the occurrence of the
> appropriate "Link:" trailers. It reasons that this does not add any
> burden on the maintainers/bug fix authors as this is already mandated by
> the "Submitting patches" guide. In fact however, the guide encourages
> using "Link:" tags for related discussions or issues which the patch
> fixes only partially, recommending "Closes:" for full resolutions.
>
> Despite it not being mentioned anywhere in the "Handling regressions"
> guide, regzbot does in fact take the "Closes:" tags into account and
> seems to in fact treat them fully equivalently to "Link:" tags.
>
> Clarify this in the regressions handling guide by always mentioning both
> of the tags.
Many thx for this and the other patch. I had planned to do something
like this myself, but never got around to.
There is just one thing that makes me slightly unhappy: this tells
readers that they can use both, but leaves the question "what's the
difference" respectively "in which situation should I use one or the
other" unanswered.
To answer that question: in a ideal world developers would use "Closes:"
when a change resolves an issue, and "Link" when it's somehow related to
a report, but not resolving the problem.
But we don't live in that world and I wonder if we ever reach that point
where regzbot could act accordingly. Nevertheless I'd say it would be
wise to write the docs towards that ideal world. E.g.: tell developers
to uses 'Closes:', but in some places briefly hint that "'Link:' works
for now, too".
I also find the patch description a bit verbose; and it would be good to
turn the text upside down: first outline what the patch, then maybe
describe the "why".
Ciao, Thorsten
next prev parent reply other threads:[~2024-04-01 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 19:29 [PATCH 0/2] regressions documentation improvements Karel Balej
2024-03-28 19:29 ` [PATCH 1/2] docs: *-regressions.rst: unify quoting, add missing word Karel Balej
2024-04-03 14:13 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-10 21:03 ` Jonathan Corbet
2024-03-28 19:29 ` [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too Karel Balej
2024-04-01 8:38 ` Thorsten Leemhuis [this message]
2024-04-01 15:19 ` Randy Dunlap
2024-04-02 9:27 ` Thorsten Leemhuis
2024-04-02 10:13 ` Karel Balej
2024-04-03 14:13 ` Thorsten Leemhuis
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=dfa22ac1-36e9-48da-a2a8-8d7818c09187@leemhuis.info \
--to=linux@leemhuis.info \
--cc=balejk@matfyz.cz \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=workflows@vger.kernel.org \
/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