From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Amir Goldstein <amir73il@gmail.com>,
lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Carlos Maiolino <cmaiolino@redhat.com>
Subject: Re: [LSF/MM TOPIC] [LSF/MM ATTEND] XFS reflink, rmap and CoW
Date: Mon, 19 Dec 2016 15:28:10 -0800 [thread overview]
Message-ID: <20161219232810.GF7311@birch.djwong.org> (raw)
In-Reply-To: <20161219231202.GP4326@dastard>
On Tue, Dec 20, 2016 at 10:12:02AM +1100, Dave Chinner wrote:
> On Thu, Dec 15, 2016 at 11:55:05PM -0800, Christoph Hellwig wrote:
> > XFS reflinks and dedup is a feature that's done already, no real need
> > to have further discussion in the big room at LSF/MM.
> >
> > That being said it would be great to have another XFS developers
> > gathering, and I could arrange one around LSM/MM. A BOF a Vault would
> > be an idea for example.
>
> I won't be there.
>
> I'll be thinking of y'all sitting inside a stuffy room in yet
> another anonymous conference center. I'm going to be out in the
> forest at the bottom of a long hill on an old highway marshalling
> race cars onto the starting line....
/me looks forward to LSF 2018: "Dave's Back Yard"
--D
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
next prev parent reply other threads:[~2016-12-19 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 6:57 [LSF/MM TOPIC] [LSF/MM ATTEND] XFS reflink, rmap and CoW Amir Goldstein
2016-12-16 7:55 ` Christoph Hellwig
2016-12-16 10:27 ` Carlos Maiolino
2016-12-19 23:12 ` Dave Chinner
2016-12-19 23:28 ` Darrick J. Wong [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-15 12:30 Carlos Maiolino
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=20161219232810.GF7311@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=amir73il@gmail.com \
--cc=cmaiolino@redhat.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--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).