From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: "Daniel Vetter" <daniel@ffwll.ch>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Thorsten Leemhuis" <linux@leemhuis.info>,
"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>,
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: Fri, 17 Mar 2023 14:56:37 -0400 [thread overview]
Message-ID: <20230317185637.ebxzsdxivhgzkqqw@meerkat.local> (raw)
In-Reply-To: <7974f3ec-3f17-c21c-139b-fd5651871a75@tessares.net>
On Fri, Mar 17, 2023 at 07:41:04PM +0100, Matthieu Baerts wrote:
> @Konstantin: would it be OK for your future Bugzilla bot to deal with
> the generic "Link:" tag instead of the specific "Closes:" one?
Yes and no -- we can easily figure out that "it's a bugzilla link and it
points at this bug", but we can't make any decisions based on it. Just because
it's a bug that is mentioned in a commit doesn't really mean that the bug is
fixed and we should close it.
E.g. it could be something like:
foo: initial workaround for bar
This implements a workaround for problems with bar (see bug link below).
It's not a complete fix, so further work is required to address all issues
identified in the bug report.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=5551212
It would be wrong here to auto-close this bug, but we can certainly add a new
comment that says:
This bug was mentioned in commit abcd1234:
https://git.kernel.org/linus/abcd1234
-K
next prev parent reply other threads:[~2023-03-17 18:58 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 [this message]
2023-03-16 16:22 ` Konstantin Ryabitsev
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=20230317185637.ebxzsdxivhgzkqqw@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 \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).