From: Ben Myers <bpm@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] xfs: remaining 3.11 merge patches
Date: Tue, 9 Jul 2013 16:09:41 -0500 [thread overview]
Message-ID: <20130709210941.GV32736@sgi.com> (raw)
In-Reply-To: <1373403841-16612-1-git-send-email-david@fromorbit.com>
Hey Dave,
On Wed, Jul 10, 2013 at 07:03:58AM +1000, Dave Chinner wrote:
> I figured it was easiest for you to just repost all three remainng
> patches for the 3.11 merge window that I have in one set. The dquot
> log res patch has been updated to address Chandra's review.
Much appreciated!
Thanks,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-07-09 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 21:03 [PATCH 0/3] xfs: remaining 3.11 merge patches Dave Chinner
2013-07-09 21:03 ` [PATCH 1/3] xfs: update mount options documentation Dave Chinner
2013-07-09 21:37 ` Ben Myers
2013-07-10 0:24 ` Dave Chinner
2013-07-09 21:04 ` [PATCH 2/3] xfs: remove local fork format handling from xfs_bmapi_write() Dave Chinner
2013-07-09 21:04 ` [PATCH 3/3] xfs: dquot log reservations are too small Dave Chinner
2013-07-09 21:09 ` Ben Myers [this message]
2013-07-09 21:55 ` [PATCH 0/3] xfs: remaining 3.11 merge patches Ben Myers
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=20130709210941.GV32736@sgi.com \
--to=bpm@sgi.com \
--cc=david@fromorbit.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