From: Steven Rostedt <rostedt@goodmis.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: ksummit@lists.linux.dev, tech-board-discuss@lists.linux-foundation.org
Subject: Re: [MAINTAINERS SUMMIT] Maintainers Support Group
Date: Tue, 19 Sep 2023 13:21:12 -0400 [thread overview]
Message-ID: <20230919132112.19b700df@gandalf.local.home> (raw)
In-Reply-To: <dbeb5ad9-fa6d-4633-a160-6a0f8ed6bd51@acm.org>
On Tue, 19 Sep 2023 10:03:48 -0700
Bart Van Assche <bvanassche@acm.org> wrote:
> On 9/19/23 09:10, Steven Rostedt wrote:
> > Thoughts?
>
> Maybe maintainers who are stressed out will prefer a video call or IRC
> session instead of sending an email that gets archived who-knows-where?
As I replied to Shuah. There would be no mailing list. And the names of the
supporting volunteers will be listed. Sure, we can include irc contacts of
how to reach those maintainers if they choose.
-- Steve
next prev parent reply other threads:[~2023-09-19 17:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 16:10 Steven Rostedt
2023-09-19 16:52 ` [Tech-board-discuss] " Shuah
2023-09-19 17:19 ` Steven Rostedt
2023-09-19 17:29 ` Steven Rostedt
2023-09-19 17:54 ` James Bottomley
2023-09-19 21:26 ` Shuah
2023-09-19 20:39 ` Theodore Ts'o
2023-09-19 21:02 ` Steven Rostedt
2023-09-20 12:03 ` Christian Brauner
2023-09-19 22:01 ` Theodore Ts'o
2023-09-19 22:07 ` Randy Dunlap
2023-09-19 22:40 ` Shuah
2023-09-19 22:32 ` Shuah
2023-09-19 22:53 ` Shuah
2023-09-19 17:03 ` Bart Van Assche
2023-09-19 17:21 ` Steven Rostedt [this message]
2023-09-19 22:55 ` Shuah
2023-09-19 23:21 ` Steven Rostedt
2023-09-20 7:06 ` Linus Walleij
2023-09-21 7:15 ` Jonathan Cameron
2023-09-20 19:52 ` Shuah
2023-09-20 22:54 ` Laurent Pinchart
2023-09-21 0:45 ` Shuah
2023-09-21 12:40 ` Linus Walleij
2023-09-21 12:56 ` Laurent Pinchart
2023-09-20 15:45 ` Mark Brown
2023-10-05 18:08 ` Jason Gunthorpe
2023-10-06 20:47 ` Linus Walleij
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=20230919132112.19b700df@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bvanassche@acm.org \
--cc=ksummit@lists.linux.dev \
--cc=tech-board-discuss@lists.linux-foundation.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