[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230317185637.ebxzsdxivhgzkqqw@meerkat.local>
Date: Fri, 17 Mar 2023 14:56:37 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Matthieu Baerts <matthieu.baerts@...sares.net>
Cc: Daniel Vetter <daniel@...ll.ch>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Thorsten Leemhuis <linux@...mhuis.info>,
Jonathan Corbet <corbet@....net>,
Andy Whitcroft <apw@...onical.com>,
Joe Perches <joe@...ches.com>,
Dwaipayan Ray <dwaipayanray1@...il.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Kai Wasserbäch <kai@....carbon-project.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Airlie <airlied@...il.com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
mptcp@...ts.linux.dev
Subject: Re: [PATCH 0/2] docs & checkpatch: allow Closes tags with links
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
Powered by blists - more mailing lists