From: Pavel Emelyanov <xemul@parallels.com>
To: viro@ZenIV.linux.org.uk
Cc: Christoph Hellwig <hch@infradead.org>,
Dmitry Monakhov <dmonakhov@openvz.org>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
tytso@mit.edu, adilger@sun.com, jack@suse.cz,
david@fromorbit.com, xemul@openvz.org
Subject: Re: Ping to Al
Date: Fri, 30 Apr 2010 16:14:13 +0400 [thread overview]
Message-ID: <4BDAC995.2040005@parallels.com> (raw)
In-Reply-To: <20100413181450.GA5720@infradead.org>
> As long as you still have the awkward ifdefs and different semantics for
> "isolation" vs "not" there's still a NACK from me. But in the end Al
> will have to decide if he wants to take your patches or not.
Hi, Al!
Regardless of the Christof's concern about the awkward ifdefs and semantics (we
will fix this for sure), can you comment anything on the patchset please.
Thanks,
Pavel
prev parent reply other threads:[~2010-04-30 17:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 14:02 [PATCH 0/5] RFC: introduce extended inode owner identifier v6 Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 1/5] vfs: Add additional owner identifier Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 2/5] quota: Implement project id support for generic quota Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 4/5] ext4: add project quota support Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 5/5] ext4: add isolated project support Dmitry Monakhov
2010-03-18 21:25 ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Andreas Dilger
2010-03-19 8:16 ` Dmitry Monakhov
2010-04-06 9:00 ` Ping Dmitry Monakhov
2010-04-13 18:14 ` Ping Christoph Hellwig
2010-04-15 11:30 ` Ping Dmitry Monakhov
2010-05-15 9:34 ` Ping Al Viro
2010-04-30 12:14 ` Pavel Emelyanov [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=4BDAC995.2040005@parallels.com \
--to=xemul@parallels.com \
--cc=adilger@sun.com \
--cc=david@fromorbit.com \
--cc=dmonakhov@openvz.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
--cc=xemul@openvz.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.