Ksummit-Discuss Archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Kernel Summit 2017 Feedback Thread
Date: Tue, 31 Oct 2017 16:29:37 +0000	[thread overview]
Message-ID: <20171031162937.cjlpmwzaxpjmmpqk@sirena.co.uk> (raw)
In-Reply-To: <20171030220652.mintguegkoln4vgz@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 801 bytes --]

On Mon, Oct 30, 2017 at 06:06:52PM -0400, Theodore Ts'o wrote:

> It was announced several months ago on the ksummit-discuss list when
> we sent out the call for Maintainer's Summit and Kernel Summit topics.

...

> be interested was on ksummit-discuss anyway.  Also, this was a
> continuation of the Kernel Summit "Open Day", where the technical
> track was open to all attendees of the colocated conference (e.g.,
> Plumbers in Santa Fe, Linux Con Korea in Seoul, etc.) in previous
> years.

I suspect that continuing to call it Kernel Summit and Kernel Summit
Open Day(s) might've avoided some of the confusion - I know it took me a
while to register that Kernel Summit was now the open part of things and
there was a new name for the invite only bit.  Perhaps that'll be
clearer next year though.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2017-10-31 16:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-29 10:12 [Ksummit-discuss] Kernel Summit 2017 Feedback Thread Theodore Ts'o
2017-10-30 12:41 ` Michael Kerrisk (man-pages)
2017-10-30 19:36   ` Theodore Ts'o
2017-10-30 15:26 ` Laura Abbott
2017-10-30 19:41   ` Theodore Ts'o
2017-10-30 20:09     ` Arnd Bergmann
2017-10-30 22:06       ` Theodore Ts'o
2017-10-30 22:19         ` Shuah Khan
2017-10-31 16:29         ` Mark Brown [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:
  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=20171031162937.cjlpmwzaxpjmmpqk@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tytso@mit.edu \
    /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).