From: Jan Kara <jack@suse.cz>
To: Li Xi <pkuelelixi@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Andreas Dilger <adilger@dilger.ca>, Jan Kara <jack@suse.cz>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"hch@infradead.org" <hch@infradead.org>,
Dmitry Monakhov <dmonakhov@openvz.org>
Subject: Re: [v16 0/4] ext4: add project quota support
Date: Wed, 13 Jan 2016 10:52:37 +0100 [thread overview]
Message-ID: <20160113095237.GE14630@quack.suse.cz> (raw)
In-Reply-To: <CAPTn0cCSzqKfS5g7Y9ESmw4wMnD2H7XCepA3drRvXH_+PN85AA@mail.gmail.com>
Hi!
On Wed 13-01-16 09:15:51, Li Xi wrote:
> BTW, I have a patch of quota-tools.git that adds project quota support
> for quota tools.
> Do you know which mail list should I send that patch to?
Send it to me, I'm quota-tools maintainer. Alternatively you can add it to
http://sourceforge.net/projects/linuxquota/, Tickets->Patches. But I prefer
simple email.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2016-01-13 9:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 8:56 [v16 0/4] ext4: add project quota support Li Xi
2016-01-12 8:56 ` [v16 1/4] ext4: adds project ID support Li Xi
2016-01-12 8:56 ` [v16 2/4] ext4: adds project quota support Li Xi
2016-01-12 9:30 ` kbuild test robot
2016-01-12 11:05 ` kbuild test robot
2016-01-18 0:07 ` kbuild test robot
2016-01-12 8:56 ` [v16 3/4] ext4: adds FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR interface support Li Xi
2016-01-18 0:16 ` kbuild test robot
2016-01-12 8:56 ` [v16 4/4] ext4: cleanup inode flag definitions Li Xi
2016-01-12 17:45 ` [v16 0/4] ext4: add project quota support Theodore Ts'o
2016-01-13 1:15 ` Li Xi
2016-01-13 3:12 ` Li Xi
2016-01-13 9:52 ` Jan Kara [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=20160113095237.GE14630@quack.suse.cz \
--to=jack@suse.cz \
--cc=adilger@dilger.ca \
--cc=dmonakhov@openvz.org \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=pkuelelixi@gmail.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).