From: Thorsten Leemhuis <linux@leemhuis.info>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Steven Rostedt <rostedt@goodmis.org>,
"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: Re: [TECH TOPIC] regressions: our workflows are the biggest enemy
Date: Thu, 13 Jun 2024 12:32:07 +0200 [thread overview]
Message-ID: <f7ffc189-6ac5-402a-a8ff-fe89304b4dd3@leemhuis.info> (raw)
In-Reply-To: <f6kqhk72iujjugt3nb7wsiz523meti6hnfzptukjpqjvkybckv@e32yogihxcch>
On 12.06.24 20:35, Liam R. Howlett wrote:
> * Thorsten Leemhuis <linux@leemhuis.info> [240612 12:08]:
>> On 12.06.24 17:50, Guenter Roeck wrote:
>>> On 6/12/24 08:26, Steven Rostedt wrote:
>>>> On Wed, 12 Jun 2024 08:34:42 +0200
>>>> Thorsten Leemhuis <linux@leemhuis.info> wrote:
>
>>>> I think this should be discussed
>>>> at Maintainers Summit, and perhaps we should start "encouraging" people
>>>> to change their workflows. Especially if we have hard data showing
>>>> that it's not working.
> [...]
> Although, I'm a little concerned about what I'm singing up for here...
See the four maintainers summit proposals I just sent for an impression
where I see trouble and how to fix that:
https://lore.kernel.org/all/c6be1b86-f224-417c-a501-6c778999a04f@leemhuis.info/
Ohh, and btw for those that worry that their subsystem is one that from
my point of view is not handling regressions well: if mails from my
other email account (the one dedicated to regressions tracking) rarely
show up in your inbox/your subsystem's mailing list, then things are
most likely fine.
Ciao, Thorsten
next prev parent reply other threads:[~2024-06-13 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 6:34 Thorsten Leemhuis
2024-06-12 15:26 ` Steven Rostedt
2024-06-12 15:50 ` Guenter Roeck
2024-06-12 16:07 ` Thorsten Leemhuis
2024-06-12 18:35 ` Liam R. Howlett
2024-06-13 10:32 ` Thorsten Leemhuis [this message]
2024-06-12 18:37 ` Leon Romanovsky
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=f7ffc189-6ac5-402a-a8ff-fe89304b4dd3@leemhuis.info \
--to=linux@leemhuis.info \
--cc=Liam.Howlett@oracle.com \
--cc=ksummit@lists.linux.dev \
--cc=linux@roeck-us.net \
--cc=rostedt@goodmis.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