Linux Kernel Summit discussions
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy6545@gmail.com>
To: Boaz Harrosh <boaz@plexistor.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Draft Kernel Summit track agenda
Date: Thu, 8 Nov 2018 13:05:41 -0500	[thread overview]
Message-ID: <CAFhKne9m5WH+4MBHJn8jmBxNwpB0GZyvRgj0sR=EV-_u3N7epg@mail.gmail.com> (raw)
In-Reply-To: <6d3fa1f2-43a6-cd34-208d-c02c68ec9dea@plexistor.com>

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

In that email, please tell us what's changed since last April!

On Thu., Nov. 8, 2018, 12:31 Boaz Harrosh <boaz@plexistor.com wrote:

> On 08/11/18 18:05, Theodore Y. Ts'o wrote:
> > On Thu, Nov 08, 2018 at 02:28:35PM +0200, Boaz Harrosh wrote:
> >>
> >> I would like to please ask again for a slot to talk about ZUFS, at one
> of the TBD
> >> slots above?
> >>
> >> It is a very big project, that I would love to discuss with the Linux
> community
> >> and developers. I believe it is a very important project in the up
> coming years.
> >
> > So for anyone who wants to schedule one the TBD / Unconference slots,
> > please send a note to the ksummit-discuss list with a [TOPIC] subject
> > prefix.  That note should include a description of what will be
> > discussed, and what the goals / success criteria for that session.
> > Also please include scheduling conflicts and/or a suggested time slot
> > that you would prefer.
> >
> > Scheduling will be based by people responding to the mail thread ---
> > especially people who will actually *be* at the Plumber's Conference
> > in vancouver.  If there's general interest and a set of issues where
> > face to face discussion would be constructive, those topics will be
> > given priority over people who just want to publicize their project or
> > just give a status update.  Status updates can always be very
> > effectively given via e-mail.  :-)
> >
> > I and other members of the program committee will be monitoring the
> > mailing list during the conference, so the same procedure should be
> > used next week.  For now though, I'd like to keep the remaining
> > sessions unscheduled to give everyone a fair shot at the remaining
> > slots.  So for people who want to propose topics, please submit
> > [TOPIC] suggestions to the ksummit mailing list.  We'll do another
> > review and scheduling pass next week on Monday, right before the
> > conference starts.
> >
>
> Cool thanks I will resend my [TOPIC]
>
> > Cheers,
> >
> >                                               - Ted
>
> Boaz
>
>
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
>

[-- Attachment #2: Type: text/html, Size: 3030 bytes --]

      reply	other threads:[~2018-11-08 18:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 17:47 [Ksummit-discuss] Draft Kernel Summit track agenda Theodore Y. Ts'o
2018-11-07 21:05 ` Thomas Gleixner
2018-11-07 21:53 ` Theodore Y. Ts'o
2018-11-08 10:06 ` Greg KH
2018-11-08 12:28 ` Boaz Harrosh
2018-11-08 15:40   ` Greg KH
2018-11-08 16:05   ` Theodore Y. Ts'o
2018-11-08 17:31     ` Boaz Harrosh
2018-11-08 18:05       ` Matthew Wilcox [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='CAFhKne9m5WH+4MBHJn8jmBxNwpB0GZyvRgj0sR=EV-_u3N7epg@mail.gmail.com' \
    --to=willy6545@gmail.com \
    --cc=boaz@plexistor.com \
    --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).