From: Thorsten Leemhuis <linux@leemhuis.info>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "workflows@vger.kernel.org" <workflows@vger.kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Bugbot for all kernel bugs?
Date: Mon, 10 Jul 2023 19:28:26 +0200 [thread overview]
Message-ID: <8133fcf4-5ed6-204a-ceb1-ee4136e32fb4@leemhuis.info> (raw)
Hi Konstantin. Is there any hope that bugbot will be usable for all
kernel bugs in bugzilla.kernel.org soon? It sounded some weeks ago like
that wasn't too far away, that's why I wonder if we might have arrived
at a point where this support could be enabled.
Sorry for bothering you about this, but I'm getting a bit tired by all
that tedious man-in-the-middle between reporters and developers to let
one group know about things the other did...
Ciao, Thorsten
next reply other threads:[~2023-07-10 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 17:28 Thorsten Leemhuis [this message]
2023-07-11 20:43 ` Konstantin Ryabitsev
2023-07-13 11:45 ` Thorsten Leemhuis
2023-07-14 20:19 ` Konstantin Ryabitsev
2023-07-15 11:30 ` Thorsten Leemhuis
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=8133fcf4-5ed6-204a-ceb1-ee4136e32fb4@leemhuis.info \
--to=linux@leemhuis.info \
--cc=konstantin@linuxfoundation.org \
--cc=regressions@lists.linux.dev \
--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