All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: linux-doc@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	workflows@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [RFC PATCH v1 1/2] docs: add a document about regression handling
Date: Mon, 3 Jan 2022 09:55:54 -0800	[thread overview]
Message-ID: <20220103095554.34602944@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> (raw)
In-Reply-To: <122bf6e0-8e1f-6567-252e-5120b3f8a573@leemhuis.info>

On Mon, 3 Jan 2022 18:20:23 +0100 Thorsten Leemhuis wrote:
> On 03.01.22 18:07, Jakub Kicinski wrote:
> > On Mon,  3 Jan 2022 10:50:50 +0100 Thorsten Leemhuis wrote:  
> >> +How to see which regressions regzbot tracks currently?
> >> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >> +
> >> +Check `regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_
> >> +for the latest info; alternatively, `search for the latest regression report
> >> +<https://lore.kernel.org/lkml/?q=%22Linux+regressions+report%22+f%3Aregzbot>`_,
> >> +which regzbot normally sends out once a week on Sunday evening (UTC), which is a
> >> +few hours before Linus usually publishes new (pre-)releases.  
> > 
> > Cool, I wonder if it would be a useful feature to be able to filter by
> > mailing lists involved or such to give maintainers a quick overview of
> > regressions they are on the hook for?  
> 
> Ha, that's a great idea, many thx. I have been scratching my head for a
> while already how to give maintainers a better overview, but the only
> thing I came up with was "check the merge path a commit causing the
> regression took", which has a few obvious downsides (it for example
> won't work if the culprit is not known yet). This should work a lot better.
> 
> But be warned, will likely take a few weeks (months?) before I get to
> implement that: I have less time to work on the regzbot code than in the
> past weeks, as I have to take care of a few other things first (most of
> them related to regzbot).

No worries, do ping when you got it ready tho :)

  reply	other threads:[~2022-01-03 17:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03  9:50 [RFC PATCH v1 0/2] docs: add a document dedicated to regressions Thorsten Leemhuis
2022-01-03  9:50 ` [RFC PATCH v1 1/2] docs: add a document about regression handling Thorsten Leemhuis
2022-01-03 17:07   ` Jakub Kicinski
2022-01-03 17:20     ` Thorsten Leemhuis
2022-01-03 17:55       ` Jakub Kicinski [this message]
2022-01-04 14:17   ` Lukas Bulwahn
2022-01-04 17:57     ` Thorsten Leemhuis
2022-01-05  8:45       ` Lukas Bulwahn
2022-01-03  9:50 ` [RFC PATCH v1 2/2] docs: regressions.rst: rules of thumb for handling regressions Thorsten Leemhuis
2022-01-04 12:16   ` Lukas Bulwahn
2022-01-04 13:29     ` Thorsten Leemhuis
2022-01-04 14:42       ` Jonathan Corbet
2022-01-04 15:09         ` Randy Dunlap
2022-01-04 18:02           ` Thorsten Leemhuis
2022-01-03 14:01 ` [RFC PATCH v1 0/2] docs: add a document dedicated to regressions Greg Kroah-Hartman

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=20220103095554.34602944@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net \
    --to=kuba@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.