From: Thorsten Leemhuis <linux@leemhuis.info>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
workflows@vger.kernel.org, aros@gmx.com,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
tools@linux.kernel.org
Cc: Kalle Valo <kvalo@kernel.org>
Subject: Re: Introducing bugbot
Date: Sat, 8 Apr 2023 14:10:40 +0200 [thread overview]
Message-ID: <1f0ebf13-ab0f-d512-6106-3ebf7cb372f1@leemhuis.info> (raw)
In-Reply-To: <gmnswy45efztvcyc3xqymm52h7cdfwjz64go2wy3zyeqcqwb76@36fva4hyip4q>
CCing Kalle (JFYI)
On 03.04.23 23:45, Konstantin Ryabitsev wrote:
>
> 2. Start mailing list threads from pre-triaged bugzilla bugs. This works the
> opposite way and creates mailing list threads based on bug reports filed in
> bugzilla. The useful things here are:
>
> - bugbot only gets triggered on open bugs in Linux/Kernel that have the
> "bugbot" flag set to "+", which allows pre-triaging a bug before bugbot
> sends it to the mailing list
> [...]
Are there any policies or best practices on how people should/are
allowed to use this? From what I can see it seems one needs to change
the Product/Component of the bug to start a thread. I wonder if a few
maintainers that are active in bugzilla might be annoyed by this, as
that might break their workflow.
Which puts me in an awkward position when I see regressions reports in
bugzilla and would like to create threads for them. Using bugbot would
be better then the manual forwards I do now, like this one:
https://lore.kernel.org/all/ed31b6fe-e73d-34af-445b-81c5c644d615@leemhuis.info/
But here I decided to *not* use bugbot, as I know Kalle sometimes is
active in bugzilla -- and thus might hate it, if I re-categorize the bug.
Ciao, Thorsten
next prev parent reply other threads:[~2023-04-08 12:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 21:45 Introducing bugbot 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
2023-04-04 17:35 ` Konstantin Ryabitsev
2023-04-04 21:39 ` David Sterba
2023-04-08 12:10 ` Thorsten Leemhuis [this message]
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=1f0ebf13-ab0f-d512-6106-3ebf7cb372f1@leemhuis.info \
--to=linux@leemhuis.info \
--cc=aros@gmx.com \
--cc=konstantin@linuxfoundation.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=tools@linux.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;
as well as URLs for NNTP newsgroup(s).