All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tao Ma <tm@tao.ma>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "Lukáš Czerner" <lczerner@redhat.com>,
	"Eric Sandeen" <sandeen@redhat.com>, "Jan Kara" <jack@suse.cz>,
	linux-ext4@vger.kernel.org
Subject: Re: Ext4 developer's get-together at Collaboration Summit/LSFMM
Date: Thu, 14 Mar 2013 11:09:32 +0800	[thread overview]
Message-ID: <51413F6C.6000308@tao.ma> (raw)
In-Reply-To: <20130313171130.GA5604@thunk.org>

On 03/14/2013 01:11 AM, Theodore Ts'o wrote:
> OK, can those people who are coming send a note answering the following questions:
> 
> 1) What time do you arrive / would you be available to attend the ext4
> workshop on Tueday?
We(Zheng and I) will arrive on Saturday, so all the time during
collaboration summit should be fine for us.
> 
> 2) What sessions (please give the time slots) on Wednesday are you
> interested in attending?
> 
> For reference, the schedule is available here:
> 
> http://events.linuxfoundation.org/events/collaboration-summit/schedule
> 
> And here are the sessions on the FS/MM track:
> 
> 9-10am	 Host-Based Disk-Mirroring with MD on Mainframe
> 10-11am	 Persistent Memory and Linux: New Storage Technologies and Interfaces
> 11:30-12:30  Using OpenLMI to Manage Storage
> 2-3pm	 The Receiving End of printk - netconsole, blockconsole, cancd
> 3-4pm    NVM Software Interfaces: New Directions
> 
> My assumption had always been that most of the Collab Summit talks
> were pretty technically lightweight[1], so other than the 4:30pm
> panel, there would be a huge amount of conflict.  But Ric assures me
> that at least some of these talks might actually have good stuff.  :-)
Top 1,2 and 5 seems to be interesting if it really cover something that
we should know about. ;)

Thanks,
Tao
> 
> Thanks!!
> 
>       	      	    	  		 - Ted
> 
> [1] Which is not a criticism; there are lots of users and system
> administrators and I/T managers who need to hear stuff that we've
> heard 100 times before, so it was just an assumption that most of the
> ext4 developers wouldn't be interested.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      parent reply	other threads:[~2013-03-14  3:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 17:24 Ext4 developer's get-together at Collaboration Summit/LSFMM Theodore Ts'o
2013-03-08 18:06 ` Ric Wheeler
2013-03-08 18:53   ` Theodore Ts'o
2013-03-08 19:32     ` Ric Wheeler
2013-03-13 12:00 ` Jan Kara
2013-03-13 16:04   ` Eric Sandeen
2013-03-13 16:13     ` Lukáš Czerner
2013-03-13 17:11       ` Theodore Ts'o
2013-03-13 17:21         ` Jan Kara
2013-03-13 17:38         ` Darrick J. Wong
2013-03-14  3:09         ` Tao Ma [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=51413F6C.6000308@tao.ma \
    --to=tm@tao.ma \
    --cc=jack@suse.cz \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --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.