From: Takashi Iwai <email@example.com> To: Thorsten Leemhuis <firstname.lastname@example.org> Cc: Greg KH <email@example.com>, Linus Torvalds <firstname.lastname@example.org>, "Rafael J. Wysocki" <email@example.com>, firstname.lastname@example.org, Linux Kernel Mailing List <email@example.com>, Konstantin Ryabitsev <firstname.lastname@example.org>, Pablo Neira Ayuso <email@example.com>, firstname.lastname@example.org, email@example.com Subject: Re: RFC: building a regression tracking bot for Linux kernel development Date: Fri, 23 Apr 2021 13:01:45 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On Fri, 23 Apr 2021 12:49:25 +0200, Thorsten Leemhuis wrote: > > On 23.04.21 12:11, Greg KH wrote: > > On Thu, Apr 22, 2021 at 09:16:40AM +0200, Thorsten Leemhuis wrote: > >> That can't be all > >> ----------------- > >> > >> Of course the world is more complicated than the simple example scenario > >> above, as the devil is always in the details. The three most obvious > >> problems the initial ideal scenario left aside: > >> > >> * The reporter doesn't specify the #regzb tag at all. Regzbot can't do > >> anything about it, it sadly won't have visionary power and a AI engine > >> any time soon. Some human (for a while that often will be me) thus needs > >> to reply with the tag with a proper reply-to to the report to make > >> regboz track it. > > > > Any specific format/tag we can use to help make this easier? Or is that > > just something that you are going to do "by hand" to start with? > > For now making sure firstname.lastname@example.org is added to the CCed of > any replies to regression reports would be a really big help to already > establish it as central place where they are all visible. Then no human > or bot needs to monitor hundreds of mailing list to find them -- which > obviously is doomed to fail and was one of the pain points when I > tracked regressions manually years ago. That sounds great. One thing I still wonder is how to populate the report from distro bug trackers. AFAIK, many reports come from there directly or indirectly. Can regzbot can have a reference to bug trackers or such? thanks, Takashi
next prev parent reply other threads:[~2021-04-23 11:01 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-22 7:16 Thorsten Leemhuis 2021-04-22 14:51 ` Mark Brown 2021-04-23 6:34 ` Thorsten Leemhuis 2021-04-23 10:11 ` Greg KH 2021-04-23 10:49 ` Thorsten Leemhuis 2021-04-23 11:01 ` Takashi Iwai [this message] 2021-04-23 11:11 ` Thorsten Leemhuis 2021-04-23 20:45 ` Guillaume Tucker 2021-04-24 9:43 ` 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: RFC: building a regression tracking bot for Linux kernel development' \ /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
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).