From: "Bill O'Donnell" <billodo@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-xfs@vger.kernel.org
Subject: [LSF/MM ATTEND] filesystems / xfs
Date: Fri, 16 Dec 2016 09:37:32 -0600 [thread overview]
Message-ID: <20161216153732.GA26958@redhat.com> (raw)
Hello-
I've been a full time XFS developer for 1.5 years, and I've
contributed to XFS in previous lives. Naturally, I'm interested
in filesystem work, particularly relating to XFS. I've also done
some work with ext4 and btrfs, and I've been comparing and
contrasting various attributes and shortcomings of these popular
offerings.
I'd like to learn more about the latest developments in reflink,
rmap and dedup, and LSF/MM provides a good forum for those
discussions. Please consider me for invitation.
Thanks-
Bill
next reply other threads:[~2016-12-16 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 15:37 Bill O'Donnell [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-16 12:30 [LSF/MM ATTEND] filesystems / xfs Brian Foster
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=20161216153732.GA26958@redhat.com \
--to=billodo@redhat.com \
--cc=linux-xfs@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).