From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: "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>,
"Thorsten Leemhuis" <linux@leemhuis.info>,
"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 1/2] docs: process: allow Closes tags with links
Date: Wed, 15 Mar 2023 14:12:05 -0400 [thread overview]
Message-ID: <20230315181205.f3av7h6owqzzw64p@meerkat.local> (raw)
In-Reply-To: <20230314-doc-checkpatch-closes-tag-v1-1-1b83072e9a9a@tessares.net>
On Wed, Mar 15, 2023 at 06:44:56PM +0100, Matthieu Baerts wrote:
> Note that thanks to this "Closes" tag, the mentioned bug trackers can
> also locate where a patch has been applied in different branches and
> repositories. If only the "Link" tag is used, the tracking can also be
> done but the ticket will not be closed and a manual operation will be
> needed.
We will soon gain this ability on bugzilla.kernel.org as one of the features
of the bugbot integration tool (which is still WIP). So, if it helps, I
support making this a recognized trailer.
Acked-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
-K
WARNING: multiple messages have this Message-ID (diff)
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Jonathan Corbet <corbet@lwn.net>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
linux-doc@vger.kernel.org,
Thorsten Leemhuis <linux@leemhuis.info>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
mptcp@lists.linux.dev
Subject: Re: [PATCH 1/2] docs: process: allow Closes tags with links
Date: Wed, 15 Mar 2023 14:12:05 -0400 [thread overview]
Message-ID: <20230315181205.f3av7h6owqzzw64p@meerkat.local> (raw)
In-Reply-To: <20230314-doc-checkpatch-closes-tag-v1-1-1b83072e9a9a@tessares.net>
On Wed, Mar 15, 2023 at 06:44:56PM +0100, Matthieu Baerts wrote:
> Note that thanks to this "Closes" tag, the mentioned bug trackers can
> also locate where a patch has been applied in different branches and
> repositories. If only the "Link" tag is used, the tracking can also be
> done but the ticket will not be closed and a manual operation will be
> needed.
We will soon gain this ability on bugzilla.kernel.org as one of the features
of the bugbot integration tool (which is still WIP). So, if it helps, I
support making this a recognized trailer.
Acked-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
-K
next prev parent reply other threads:[~2023-03-15 18:12 UTC|newest]
Thread overview: 35+ 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 ` Matthieu Baerts
2023-03-15 17:44 ` [PATCH 1/2] docs: process: " Matthieu Baerts
2023-03-15 17:44 ` Matthieu Baerts
2023-03-15 18:12 ` Konstantin Ryabitsev [this message]
2023-03-15 18:12 ` Konstantin Ryabitsev
2023-03-15 18:29 ` Matthieu Baerts
2023-03-15 18:29 ` Matthieu Baerts
2023-03-15 18:19 ` Jonathan Corbet
2023-03-15 18:19 ` Jonathan Corbet
2023-03-15 18:28 ` Matthieu Baerts
2023-03-15 18:28 ` Matthieu Baerts
2023-03-15 19:12 ` Andrew Morton
2023-03-15 19:12 ` Andrew Morton
2023-03-17 8:00 ` Bagas Sanjaya
2023-03-17 8:00 ` Bagas Sanjaya
2023-03-20 9:07 ` Matthieu Baerts
2023-03-20 9:07 ` Matthieu Baerts
2023-03-15 17:44 ` [PATCH 2/2] checkpatch: " Matthieu Baerts
2023-03-15 17:44 ` Matthieu Baerts
2023-03-15 19:25 ` checkpatch: allow Closes tags with links: Tests Results MPTCP CI
2023-03-16 9:22 ` [PATCH 0/2] docs & checkpatch: allow Closes tags with links Thorsten Leemhuis
2023-03-16 9:22 ` Thorsten Leemhuis
2023-03-16 11:43 ` Matthieu Baerts
2023-03-16 11:43 ` Matthieu Baerts
2023-03-16 17:30 ` Linus Torvalds
2023-03-16 17:30 ` Linus Torvalds
2023-03-17 16:58 ` Daniel Vetter
2023-03-17 16:58 ` Daniel Vetter
2023-03-17 18:41 ` Matthieu Baerts
2023-03-17 18:41 ` Matthieu Baerts
2023-03-17 18:56 ` Konstantin Ryabitsev
2023-03-17 18:56 ` Konstantin Ryabitsev
2023-03-16 16:22 ` Konstantin Ryabitsev
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=20230315181205.f3av7h6owqzzw64p@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.