From: "Lukáš Czerner" <lczerner@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org
Subject: Re: Ext4 meeting around LSF
Date: Tue, 11 Feb 2014 14:28:40 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1402111428030.2225@localhost.localdomain> (raw)
In-Reply-To: <20140210233453.GB25308@thunk.org>
Hi,
I am actually leaving Friday morning, so everything other than
Friday 28th works for me.
Thanks!
-Lukas
On Mon, 10 Feb 2014, Theodore Ts'o wrote:
> Date: Mon, 10 Feb 2014 18:34:53 -0500
> From: Theodore Ts'o <tytso@mit.edu>
> To: Darrick J. Wong <darrick.wong@oracle.com>
> Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
> Subject: Re: Ext4 meeting around LSF
>
> On Mon, Feb 10, 2014 at 03:19:17PM -0800, Darrick J. Wong wrote:
> > Has the date of the ext4 meeting been settled? I can attend as long as it's
> > not on Thursday, March 27th.
>
> We're curently negotiating the date. Eric can't make Friday, and for
> some reason Craig isn't all that enthused about Thursday. We may end
> up having to do it on Wendesday. Is there some Oracle-related meeting
> on Thursday that would make it impossible for you and Mingming to attend?
>
> - Ted
> --
> 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
>
prev parent reply other threads:[~2014-02-11 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 11:58 Ext4 meeting around LSF Jan Kara
2014-01-11 18:05 ` Theodore Ts'o
2014-01-13 5:45 ` Jan Kara
2014-01-15 16:20 ` Ext4 (and xfs and btrfs?) meetings " Ric Wheeler
2014-02-10 23:19 ` Ext4 meeting " Darrick J. Wong
2014-02-10 23:34 ` Theodore Ts'o
2014-02-10 23:45 ` Darrick J. Wong
2014-02-11 13:28 ` Lukáš Czerner [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=alpine.LFD.2.00.1402111428030.2225@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.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 NNTP newsgroup(s).