From: Fengguang Wu <fengguang.wu@intel.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: 2012 Kernel Summit: Call for Participation: 2nd CALL
Date: Mon, 25 Jun 2012 22:47:29 +0800 [thread overview]
Message-ID: <20120625144729.GB6876@localhost> (raw)
In-Reply-To: <20120622181853.GI4642@google.com>
On Fri, Jun 22, 2012 at 11:18:53AM -0700, Tejun Heo wrote:
> Hey again.
>
> On Thu, Jun 21, 2012 at 11:11:12AM -0700, Tejun Heo wrote:
> > Depending on the number of people affected and if at all possible, it
> > would be nice to avoid such big holidays. So, have fun, guys.
>
> Eh never mind. Minchan just told me KS is in August and Thanksgiving
> is in Sept. Stupid me. :)
Aha, so you don't have that 1.5-month long travel season like us ;)
Thanks,
Fengguang
next prev parent reply other threads:[~2012-06-25 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 15:19 2012 Kernel Summit: Call for Participation: 2nd CALL Theodore Ts'o
2012-06-21 3:28 ` NeilBrown
2012-06-21 18:11 ` Tejun Heo
2012-06-22 2:03 ` Kukjin Kim
2012-06-22 18:18 ` Tejun Heo
2012-06-25 14:47 ` Fengguang Wu [this message]
2012-06-25 17:23 ` Tejun Heo
2012-06-25 14:43 ` Fengguang Wu
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=20120625144729.GB6876@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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