All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
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: Wed, 13 Mar 2013 18:21:24 +0100	[thread overview]
Message-ID: <20130313172124.GA17469@quack.suse.cz> (raw)
In-Reply-To: <20130313171130.GA5604@thunk.org>

On Wed 13-03-13 13:11:30, Ted Tso 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?
  As I said, I arrive Monday afternoon. So yes, Tuesday is OK with me.

> 2) What sessions (please give the time slots) on Wednesday are you
> interested in attending?
  Nothing really critical, but if Ric promises talk at 3pm will be
interesting then I might have a peek there ;) But ext4 get-together has a
priority for me.

> For reference, the schedule is available here:
> 
> http://events.linuxfoundation.org/events/collaboration-summit/schedule
  Somehow the connection to collaborationsummit2013.sched.org always
timeouts for me. Strange.
 
								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2013-03-13 17:21 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 [this message]
2013-03-13 17:38         ` Darrick J. Wong
2013-03-14  3:09         ` Tao Ma

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=20130313172124.GA17469@quack.suse.cz \
    --to=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.