From: James Bottomley <James.Bottomley@SteelEye.com>
To: Ric Wheeler <ric@emc.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
xfs@oss.sgi.com, reiserfs-list@namesys.com,
ext2-devel@lists.sourceforge.net, linux-ide@vger.kernel.org,
ocfs2-devel@oss.oracle.com, linux-scsi@vger.kernel.org,
lsf07pc@usenix.org
Subject: Re: CFP: Linux 2007 File System & IO Workshop
Date: Tue, 17 Oct 2006 18:40:34 -0400 [thread overview]
Message-ID: <1161124834.6245.51.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <4534268E.9030201@emc.com>
On Mon, 2006-10-16 at 20:40 -0400, Ric Wheeler wrote:
> On February 12-13, we have put together a combined Linux file system &
> IO 2-day workshop in San Jose, CA. Note that the USENIX File System and
> Storage Technologies conference follows us in the same venue, so we hope
> to get some interaction between the two groups as well as leverage the
> USENIX people to help us get this done.
>
> For more information, please see:
>
> http://www.usenix.org/events/lsf07/
Just to clarify, this event is a follow on to the Vancouver Storage
summit. Although USENIX is helping us to run it, you don't have to be
a USENIX member to submit a position paper. The idea of the position
papers is to give the limited number of places (for storage we've got
about 20-25 and about the same again for fs) to people who have
interesting topics they need to discuss---so if you submit, be prepared
to make a presentation of it.
James
next prev parent reply other threads:[~2006-10-17 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 0:40 CFP: Linux 2007 File System & IO Workshop Ric Wheeler
2006-10-17 22:40 ` James Bottomley [this message]
2006-10-17 23:25 ` Luben Tuikov
2006-10-18 0:00 ` James Bottomley
2006-10-18 0:50 ` Luben Tuikov
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=1161124834.6245.51.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf07pc@usenix.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=reiserfs-list@namesys.com \
--cc=ric@emc.com \
--cc=xfs@oss.sgi.com \
/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).