From: Mark Brown <broonie@kernel.org>
To: "Artem S. Tashkinov" <aros@gmx.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
workflows@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Introducing bugbot
Date: Tue, 4 Apr 2023 18:25:07 +0100 [thread overview]
Message-ID: <bb77b0aa-6595-4745-b9c8-4ee95cef610d@sirena.org.uk> (raw)
In-Reply-To: <022e2ef8-2a94-3109-ab90-9ee980915887@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
On Tue, Apr 04, 2023 at 04:16:08PM +0000, Artem S. Tashkinov wrote:
> Let's have a bot which polls open bug reports every 3-6 months with this
> question:
> "Is this still an issue in the current kernel? Please leave a comment or
> this bug report will be closed due to inactivity".
> By doing this we could make the bugzilla a whole more relevant and effective
> tool instead of having a ton of bug reports no one cares about or can even
> confirm.
> I would only exclude the bug reports of type "Enhancement".
An explicit flag to disable would also be useful if this is done at all,
these bots exceptionally frustrating with trivially reproducible issues
that don't require special hardware or anything.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-04-04 17:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 21:45 Konstantin Ryabitsev
2023-04-03 21:47 ` Kernel.org Bugbot
2023-04-03 21:51 ` Konstantin Ryabitsev
2023-04-04 5:58 ` Thorsten Leemhuis
2023-04-04 6:57 ` Geert Uytterhoeven
2023-04-04 8:16 ` Bagas Sanjaya
2023-04-04 12:36 ` Konstantin Ryabitsev
2023-04-04 12:55 ` Thorsten Leemhuis
2023-04-04 16:16 ` Artem S. Tashkinov
2023-04-04 17:25 ` Mark Brown [this message]
2023-04-04 17:35 ` Konstantin Ryabitsev
2023-04-04 21:39 ` David Sterba
2023-04-08 12:10 ` Thorsten Leemhuis
2023-04-12 12:23 ` Kalle Valo
2023-04-12 14:07 ` Konstantin Ryabitsev
2023-04-12 16:47 ` Kalle Valo
2023-05-05 15:52 ` Jakub Kicinski
2023-05-05 19:12 ` Konstantin Ryabitsev
2023-05-05 19:32 ` Jakub Kicinski
2023-05-05 19:39 ` Konstantin Ryabitsev
2023-05-05 19:43 ` Jakub Kicinski
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=bb77b0aa-6595-4745-b9c8-4ee95cef610d@sirena.org.uk \
--to=broonie@kernel.org \
--cc=aros@gmx.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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