From: Theodore Ts'o <tytso@mit.edu>
To: ksummit-discuss@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [Ksummit-discuss] Next steps and plans for the 2017 Maintainer and Kernel Summits
Date: Wed, 21 Jun 2017 01:04:52 -0400 [thread overview]
Message-ID: <20170621050452.67gnlgzmzlalb6ns@thunk.org> (raw)
In-Reply-To: <20170614132920.csogpzkl4k5k7kaj@thunk.org>
On Wed, Jun 14, 2017 at 09:29:20AM -0400, Theodore Ts'o wrote:
> We will use the rest of names that Linus had mentioned as being part
> of his secondary list to preseed the list of people to be considered.
> People who suggest topics that should be discussed on the Maintainer's
> summit will be added to the list. Please prefix [MAINTAINERS SUMMIT]
> to the subject line, and remember that we only have a half-day, and
> they should be appropriate for the Maintainer's summit --- that is,
> they should be focused on the development process.
If you are interested in attending the Maintainer's Summit, I'd
appreciate it if you could send in any topic proposals by Monday, June
26th. Many thanks!!
- Ted
next prev parent reply other threads:[~2017-06-21 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 13:29 Theodore Ts'o
2017-06-21 5:04 ` Theodore Ts'o [this message]
2017-06-27 13:23 ` Daniel Vetter
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=20170621050452.67gnlgzmzlalb6ns@thunk.org \
--to=tytso@mit.edu \
--cc=ksummit-discuss@lists.linux-foundation.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox