linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, andiry@gmail.com,
	lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] [LSF/MM TOPIC] NOVA: A log-structured file system for NVM
Date: Wed, 10 Feb 2016 08:19:56 -0800	[thread overview]
Message-ID: <1455121196.2341.13.camel@HansenPartnership.com> (raw)
In-Reply-To: <20160210111414.GF12245@quack.suse.cz>

[cc list cut to pc only]
On Wed, 2016-02-10 at 12:14 +0100, Jan Kara wrote:
>   Hi,
> 
> On Tue 09-02-16 22:15:00, Andiry Xu wrote:
> > I would like to attend LSF/MM to present a new file system design 
> > for non-volatile main memories.
> 
> Well, LSF/MM is based more on discussions than presentations. Also a 
> lot of people from LSF/MM will go to Vault so I don't think 
> presenting at LSF/MM would make much sense. But we register your
> attend request.

What's this "we" business?  Hannes added one name (Vladimir Davydov)
since I went off to do some patent litigation assistance on 4 Feb.  It
looks like we've quite a big backlog that I'm just adding now. 
 However, someone else doing it while I was away would have been
appreciated.  Even if I add the rest, we still need people to go over
the list and check I didn't miss anything.  People reply in strange
ways and our audience is apt not to kick up a fuss until they don't get
their invitation...

Thanks,

James


  parent reply	other threads:[~2016-02-10 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10  6:15 [LSF/MM ATTEND] [LSF/MM TOPIC] NOVA: A log-structured file system for NVM Andiry Xu
2016-02-10 11:14 ` [Lsf-pc] " Jan Kara
2016-02-10 16:03   ` Andiry Xu
2016-02-10 16:19   ` James Bottomley [this message]
2016-02-11 14:00     ` Jan Kara

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=1455121196.2341.13.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=andiry@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /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).