From: Rich Johnston <rjohnston@sgi.com>
To: Eric Sandeen <sandeen@redhat.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH 1/2] xfs_fsr: extra debugging info
Date: Mon, 18 Nov 2013 13:03:16 -0600 [thread overview]
Message-ID: <528A6474.4080804@sgi.com> (raw)
In-Reply-To: <5261B183.7040309@redhat.com>
This has been committed.
Thanks
--Rich
commit 275077754611e5a15672624e674265b54f1cb7ed
Author: Eric Sandeen <sandeen@redhat.com>
Date: Fri Oct 18 22:09:07 2013 +0000
xfs_fsr: extra debugging info
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-18 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 22:07 [PATCH 0/1] xfs_fsr fixes Eric Sandeen
2013-10-18 22:09 ` [PATCH 1/2] xfs_fsr: extra debugging info Eric Sandeen
2013-11-17 10:06 ` Christoph Hellwig
2013-11-18 19:03 ` Rich Johnston [this message]
2013-10-18 22:30 ` [PATCH 2/2] xfs_fsr: fix SWAPEXT failures under selinux Eric Sandeen
2013-11-17 10:08 ` Christoph Hellwig
2013-11-18 19:03 ` Rich Johnston
2013-11-15 18:49 ` [PATCH 0/1] xfs_fsr fixes Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2012-03-30 14:54 [PATCH 1/2] xfs_fsr: extra debugging info Eric Sandeen
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=528A6474.4080804@sgi.com \
--to=rjohnston@sgi.com \
--cc=sandeen@redhat.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