ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: [Ksummit-discuss] Maintainer's / Kernel Summit 2022 CFP
Date: Fri, 17 Jun 2022 08:17:07 -0400	[thread overview]
Message-ID: <20220617121707.wepd2k5yjdr75pko@meerkat.local> (raw)
In-Reply-To: <CAL_JsqLz6b_r_d96C=Q21exqq8TQg1G5GkW6ttiEUTUZ+QYBJA@mail.gmail.com>

On Thu, Jun 16, 2022 at 02:54:47PM -0600, Rob Herring wrote:
> > Linus will be generating a core list of people to be invited to the
> > Maintainers Summit.  The top ten people from that list will receive
> > invites, and then program committee will use the rest of Linus's list
> > as a starting point of people to be considered.  People who suggest
> > topics that should be discussed at the Maintainers Summit will also
> > be added to the list for consideration.  To make topic suggestions for
> > the Maintainers Summit, please send e-mail to the
> > ksummit-discuss@lists.linuxfoundation.org list with a subject prefix
> Last year we moved to ksummit@lists.linux.dev. Did we move back?
> There's posts to both lists now.

I'm equally confused. I think folks just reused the old instructions that
didn't have the updated list address.

I suggest we pretend this never happened and instruct everyone to move over to
the new list (again). The old list should really be closed with an
auto-responder telling people where they should send things now.


      parent reply	other threads:[~2022-06-17 12:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  4:25 [Ksummit-discuss] Maintainer's / Kernel Summit 2022 CFP Theodore Ts'o
2022-06-16 20:54 ` Rob Herring
2022-06-17  8:40   ` Hans de Goede
2022-06-17 12:17   ` Konstantin Ryabitsev [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220617121707.wepd2k5yjdr75pko@meerkat.local \
    --to=konstantin@linuxfoundation.org \


* 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 NNTP newsgroup(s).