From: Jakub Kicinski <kuba@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: workflows@vger.kernel.org, aros@gmx.com,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
tools@linux.kernel.org, linux@leemhuis.info
Subject: Re: Introducing bugbot
Date: Fri, 5 May 2023 12:32:26 -0700 [thread overview]
Message-ID: <20230505123226.731d8ff8@kernel.org> (raw)
In-Reply-To: <20230505-lent-swoosh-4897e2@meerkat>
On Fri, 5 May 2023 15:12:02 -0400 Konstantin Ryabitsev wrote:
> On Fri, May 05, 2023 at 08:52:18AM -0700, Jakub Kicinski wrote:
> > > Per our discussion last fall, I've been working on a bridge between bugzilla
> > > and public-inbox, which went live in the past few days. It's still a very
> > > early release, but it can do the following:
> >
> > What about closing the bugs once they had been fixed/triaged/proven
> > invalid?
>
> For now, bugbot can look at a branch in a git repo and close bugs when it sees
> a matching "Closes:" trailer.
Interesting. Obviously that assumes the bug needs a fix, and we're
talking bugzilla so lots of clueless people lobbing non-issues at us.
But also - Closes: is a legit trailer now? I thought we only allow Link:
In any case - I'm guessing I just don't have permissions to close the
issues via web. Is your preference to iterate on the bot or maintainers
to request permissions in BZ (how?)?
next prev parent reply other threads:[~2023-05-05 19:33 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
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 [this message]
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=20230505123226.731d8ff8@kernel.org \
--to=kuba@kernel.org \
--cc=aros@gmx.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--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