From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] xfsprogs: Allow pquota and gquota to be used together
Date: Fri, 02 Aug 2013 15:40:19 -0500 [thread overview]
Message-ID: <1375476019.4155.66.camel@chandra-dt.ibm.com> (raw)
In-Reply-To: <20130802015032.GY7118@dastard>
On Fri, 2013-08-02 at 11:50 +1000, Dave Chinner wrote:
> On Thu, Aug 01, 2013 at 02:24:59PM -0500, Chandra Seetharaman wrote:
> > Hello All,
> >
> > These two patches make the relevant user space changes to support
> > the gquota/pquota in kernel.
> >
> > It applies cleanly on crc-dev branch of xfsprogs.
>
> I think I've already brought all of the libxfs pquota changes across
> in the series of patches I have that unified the kernel and
> userspace code on top of the crc-dev branch....
Cool.
I just looked at your patches. Some of my changes are still not in those
patches.
I will rebase and post a new patchset once your patches are merged in.
Thanks
Chandra
>
> Cheers,
>
> Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-02 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 19:24 [PATCH 0/2] xfsprogs: Allow pquota and gquota to be used together Chandra Seetharaman
2013-08-01 19:25 ` [PATCH 1/2] xfsprogs: Remove incore use of XFS_OQUOTA_ENFD and XFS_OQUOTA_CHKD Chandra Seetharaman
2013-08-14 19:02 ` Rich Johnston
2013-08-14 21:27 ` Rich Johnston
2013-08-01 19:25 ` [PATCH 2/2] xfsprogs: Start using pquotaino from on-disk superblock Chandra Seetharaman
2013-08-14 19:03 ` Rich Johnston
2013-08-14 21:27 ` Rich Johnston
2013-08-02 1:50 ` [PATCH 0/2] xfsprogs: Allow pquota and gquota to be used together Dave Chinner
2013-08-02 20:40 ` Chandra Seetharaman [this message]
2013-08-14 21:29 ` Rich Johnston
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=1375476019.4155.66.camel@chandra-dt.ibm.com \
--to=sekharan@us.ibm.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