public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: xfs@oss.sgi.com
Subject: [LSF/MM ATTEND] xfs development and fs related topics
Date: Sat, 10 Jan 2015 10:01:48 -0500	[thread overview]
Message-ID: <20150110150148.GB13511@laptop.bfoster> (raw)

Hi,

I'd like to attend LSF this year. I'm interested in catching up with the
XFS folks on some XFS specific things such as sparse inode support (my
current work), reverse extent mapping (proposed/prototype by Dave C.),
futures, etc.

My more recent work has been around improving XFS behavior on things
like glusterfs and Ceph, so any collaboration on that front is of
interest.

Finally, as a fulltime XFS guy I'm interested in pretty much anything
generally fs related that intersects with or can draw from XFS (e.g.,
power failure/fs shutdown discussion, SMR stuff, etc.). Thanks!

Brian

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

                 reply	other threads:[~2015-01-10 15:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150110150148.GB13511@laptop.bfoster \
    --to=bfoster@redhat.com \
    --cc=lsf-pc@lists.linux-foundation.org \
    --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