All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laura Abbott <labbott@redhat.com>
To: Theodore Ts'o <tytso@mit.edu>, ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Kernel Summit 2017 Feedback Thread
Date: Mon, 30 Oct 2017 08:26:01 -0700	[thread overview]
Message-ID: <5a569d45-ef78-3ab6-1926-2359ffb2ddb9@redhat.com> (raw)
In-Reply-To: <20171029101257.wgujjxh7ert3lxl2@thunk.org>

On 10/29/2017 03:12 AM, Theodore Ts'o wrote:
> Hi,
> 
> Please reply to this thread if you have any comments about how we can
> better organize the Kernel Summit for next year (i.e., the open
> technical discussion track that was open to anyone with a Maintainer's
> Summit or OSS Europe Badge, and the "unconference track").
> 
> Note that next year the plan is that the Kernel Summit and the
> Maintainer's Summit will be colocated with the Linux Plumbers
> Conference in Philadelphia.
> 
> 					- Ted

What ended up happening in the unconference anyway? I mostly didn't
think about it but part of that was not knowing what was being
discussed. I get the nature of the unconference makes it hard to
plan ahead but there didn't seem to be a good way to know what was
being discussed.

Thanks,
Laura

  parent reply	other threads:[~2017-10-30 15:26 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 [this message]
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

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=5a569d45-ef78-3ab6-1926-2359ffb2ddb9@redhat.com \
    --to=labbott@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.