From: Ben Myers <bpm@sgi.com>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Abhijith Das <adas@redhat.com>, Jan Kara <jack@suse.cz>,
Chandra Seetharaman <sekharan@us.ibm.com>,
xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] Add a new quotactl command to support 3 quota types in XFS
Date: Wed, 21 Aug 2013 12:44:10 -0500 [thread overview]
Message-ID: <20130821174410.GC7153@sgi.com> (raw)
In-Reply-To: <1377088082.2738.19.camel@menhir>
Hi Steven,
On Wed, Aug 21, 2013 at 01:28:02PM +0100, Steven Whitehouse wrote:
> Hi,
>
> On Tue, 2013-08-20 at 17:25 -0500, Ben Myers wrote:
> > Hi Chandra,
> >
> > On Tue, Aug 06, 2013 at 05:27:06PM -0500, Chandra Seetharaman wrote:
> > > XFS now supports simultaneous use of 3 quota types (user, group,
> > > and project).
> > >
> > > In order to support this a new quotactl command is introduced
> > > in this patch series.
> >
> > I've applied patches 1 and 2 at git://oss.sgi.com/xfs/xfs.git, master branch.
> > I think patch 3 should go through the gfs2 tree.
> >
> > Steven, I think if you want to pull in patch 3 you'll also need patch 1. Maybe
> > the easiest way is to cherry pick it from the xfs tree? If you do we'll have a
> > trivial merge conflict. Anyway, it's af30cb446dd5 if you want.
> >
> > Thanks,
> > Ben
>
> I think it would be better if all the patches went through the same tree
> to save issues with dependencies. I don't mind if you want to put the
> gfs2 patches in the xfs tree to keep everything in the same place. There
> are no current quota changes in the gfs2 tree, so there should not be a
> conflict due to that.
Ok, we'll take that route. Thanks.
> Also, it would be good if Christoph's comments could be addressed too,
Agreed.
-Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-08-21 17:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 22:27 [PATCH 0/3] Add a new quotactl command to support 3 quota types in XFS Chandra Seetharaman
2013-08-06 22:27 ` [PATCH 1/3] quota: Add a new quotactl command Q_XGETQSTATV Chandra Seetharaman
2013-08-13 20:42 ` Rich Johnston
2013-08-13 20:50 ` Chandra Seetharaman
2013-08-13 21:22 ` Jan Kara
2013-08-13 22:22 ` Rich Johnston
2013-08-13 22:39 ` Chandra Seetharaman
2013-08-14 9:31 ` Jan Kara
2013-08-21 6:43 ` Christoph Hellwig
2013-08-21 13:01 ` Jan Kara
2013-08-21 18:12 ` Ben Myers
2013-08-21 18:19 ` Christoph Hellwig
2013-08-21 21:15 ` Chandra Seetharaman
2013-08-29 17:00 ` Chandra Seetharaman
2013-08-29 17:48 ` Ben Myers
2013-08-06 22:27 ` [PATCH 2/3] xfs: Add support for the Q_XGETQSTATV Chandra Seetharaman
2013-08-13 20:42 ` Rich Johnston
2013-08-06 22:27 ` [PATCH 3/3] gfs2: " Chandra Seetharaman
2013-08-13 20:42 ` Rich Johnston
2013-08-20 22:25 ` [PATCH 0/3] Add a new quotactl command to support 3 quota types in XFS Ben Myers
2013-08-21 12:28 ` Steven Whitehouse
2013-08-21 17:44 ` Ben Myers [this message]
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=20130821174410.GC7153@sgi.com \
--to=bpm@sgi.com \
--cc=adas@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sekharan@us.ibm.com \
--cc=swhiteho@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;
as well as URLs for NNTP newsgroup(s).