From: Theodore Ts'o <tytso@mit.edu>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Maintainer's Summit 2017 Feedback Thread
Date: Sun, 29 Oct 2017 06:08:16 -0400 [thread overview]
Message-ID: <20171029100816.pmq5dpmck4cclmdw@thunk.org> (raw)
Hi,
Please reply to this thread if you have any comments about how we can
organize the Maintainer's Summit for next year. Given that Linus
seemed fairly happy with how things went, it's likely we will stick
with the same format for next year, but if there are any details about
how we could do things better, I'd greatly appreciate them.
Thanks!!
- Ted
next reply other threads:[~2017-10-29 10:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 10:08 Theodore Ts'o [this message]
2017-10-30 16:29 ` [Ksummit-discuss] Maintainer's Summit 2017 Feedback Thread Bart Van Assche
2017-10-30 16:32 ` Dan Williams
2017-10-30 18:45 ` Mimi Zohar
2017-10-30 17:42 ` Bart Van Assche
2017-10-30 21:03 ` Theodore Ts'o
2017-10-30 21:20 ` Greg KH
2017-10-30 21:24 ` Konstantin Ryabitsev
2017-10-30 21:27 ` James Bottomley
2017-10-30 21:27 ` Bart Van Assche
2017-10-30 21:43 ` greg
2017-10-30 22:36 ` Julia Lawall
2017-10-30 18:46 ` Takashi Iwai
2017-10-30 23:10 ` Jiri Kosina
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=20171029100816.pmq5dpmck4cclmdw@thunk.org \
--to=tytso@mit.edu \
--cc=ksummit-discuss@lists.linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).