From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: "Matthieu Baerts" <matthieu.baerts@tessares.net>,
"Jonathan Corbet" <corbet@lwn.net>,
"Andy Whitcroft" <apw@canonical.com>,
"Joe Perches" <joe@perches.com>,
"Dwaipayan Ray" <dwaipayanray1@gmail.com>,
"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
"Kai Wasserbäch" <kai@dev.carbon-project.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, mptcp@lists.linux.dev
Subject: Re: [PATCH 0/2] docs & checkpatch: allow Closes tags with links
Date: Thu, 16 Mar 2023 12:22:27 -0400 [thread overview]
Message-ID: <20230316162227.727rhima2tejdl5j@meerkat.local> (raw)
In-Reply-To: <c27709bd-90af-ec4f-de0b-3a4536bc17ca@leemhuis.info>
On Thu, Mar 16, 2023 at 10:22:18AM +0100, Thorsten Leemhuis wrote:
> I liked Andrew's `have been using "Addresses:" on occasion. [...] more
> humble [...]` comment. Sadly that tag is not supported by GitLab and
> GitHub. But well, "Resolves" is and also a bit more humble if you ask
> me. How about using that instead? Assuming that Konstantin can work with
> that tag, too, but I guess he can.
There's a subtle difference between "Closes" and "Resolves" that may be
important to consider ("closes" doesn't really imply the bug is "fixed").
The Bugbot should eventually support a number of "if this, then that"
conditions once it's done, so which tag we look for will be a matter of
configuration. It's not yet at that stage, though I should have some initial
trials in the near future.
-K
prev parent reply other threads:[~2023-03-16 16:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 17:44 [PATCH 0/2] docs & checkpatch: allow Closes tags with links Matthieu Baerts
2023-03-15 17:44 ` [PATCH 1/2] docs: process: " Matthieu Baerts
2023-03-15 18:12 ` Konstantin Ryabitsev
2023-03-15 18:29 ` Matthieu Baerts
2023-03-15 18:19 ` Jonathan Corbet
2023-03-15 18:28 ` Matthieu Baerts
2023-03-15 19:12 ` Andrew Morton
2023-03-17 8:00 ` Bagas Sanjaya
2023-03-20 9:07 ` Matthieu Baerts
2023-03-15 17:44 ` [PATCH 2/2] checkpatch: " Matthieu Baerts
2023-03-16 9:22 ` [PATCH 0/2] docs & " Thorsten Leemhuis
2023-03-16 11:43 ` Matthieu Baerts
2023-03-16 17:30 ` Linus Torvalds
2023-03-17 16:58 ` Daniel Vetter
2023-03-17 18:41 ` Matthieu Baerts
2023-03-17 18:56 ` Konstantin Ryabitsev
2023-03-16 16:22 ` Konstantin Ryabitsev [this message]
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=20230316162227.727rhima2tejdl5j@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=kai@dev.carbon-project.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lukas.bulwahn@gmail.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
/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