From: Thorsten Leemhuis <linux@leemhuis.info>
To: ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Regression tracking & fixing: current state, problems, and next steps
Date: Fri, 16 Sep 2022 09:54:01 +0100 [thread overview]
Message-ID: <8d200ca5-7ccd-fbf5-182a-602f00e98eca@leemhuis.info> (raw)
In-Reply-To: <db597a89-1487-6a05-e2b4-24fc27bdebdd@leemhuis.info>
On 20.06.22 14:33, Thorsten Leemhuis wrote:
>
> This session is meant to complement the kernel summit session with the
> same title I just submitted separately
> (https://lore.kernel.org/ksummit/0ea86ba8-97a4-0b25-406d-ea261c82292a@leemhuis.info/
> ). The idea is to summarize in this session what has been discussed and
> agreed on in that ksummit session and further discuss issues that need
> further discussion.
If anyone is interested in the slides I showed yesterday, find them here
(note, I skipped a few because some things had come up earlier already):
http://www.leemhuis.info/files/talks/202209-kernel_maintainers_summit-regtracking.pdf
The slides for the kernel summit session I held on Wednesday can be
found here (the first section is similar, but more detailed):
https://lpc.events/event/16/contributions/1222/attachments/1105/2123/Leemhuis-regtracking.pdf
While at it, here also the links to regzbot's documentation:
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md
And for completeness, here is the link to the rendered version of
Documentation/process/handling-regressions.rst:
https://docs.kernel.org/process/handling-regressions.html
Ciao, Thorsten
prev parent reply other threads:[~2022-09-16 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 13:33 [MAINTAINERS SUMMIT] Regression tracking & fixing: current state, problems, and next steps Thorsten Leemhuis
2022-09-16 8:54 ` Thorsten Leemhuis [this message]
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=8d200ca5-7ccd-fbf5-182a-602f00e98eca@leemhuis.info \
--to=linux@leemhuis.info \
--cc=ksummit@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).