From: "Paul Menage" <menage@google.com>
To: "Christoph Hellwig" <hch@infradead.org>, linux-fsdevel@vger.kernel.org
Cc: "Alexander Viro" <viro@zeniv.linux.org.uk>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add MS_BIND_FLAGS mount flag
Date: Thu, 14 Feb 2008 07:23:21 -0800 [thread overview]
Message-ID: <6599ad830802140723t2239c432v3610d9a0fd77e862@mail.gmail.com> (raw)
In-Reply-To: <6599ad830802140722t2e3a2779sa323657dfd6da841@mail.gmail.com>
[ cc: linux-fsdevel ]
On Thu, Feb 14, 2008 at 7:22 AM, Paul Menage <menage@google.com> wrote:
> On Wed, Feb 13, 2008 at 10:02 PM, Christoph Hellwig <hch@infradead.org> wrote:
> >
> > I think this concept is reasonable, but I don't think MS_BIND_FLAGS
> > is a descriptive name for this flag. MS_EXPLICIT_FLAGS might be better
> > but still isn't optimal.
> >
>
> MS_BIND_FLAGS_OVERRIDE ?
>
> Paul
>
prev parent reply other threads:[~2008-02-14 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47B283EB.8070209@google.com>
2008-02-14 8:30 ` [PATCH] Add MS_BIND_FLAGS mount flag Miklos Szeredi
2008-02-14 13:06 ` Trond Myklebust
2008-02-14 15:19 ` Paul Menage
2008-02-14 16:03 ` Miklos Szeredi
2008-02-14 16:13 ` Paul Menage
2008-02-14 17:31 ` Miklos Szeredi
2008-02-14 18:05 ` Paul Menage
2008-02-14 22:30 ` Miklos Szeredi
2008-02-14 16:26 ` Trond Myklebust
2008-02-14 17:39 ` Miklos Szeredi
2008-02-14 19:17 ` Trond Myklebust
2008-02-14 22:18 ` Miklos Szeredi
2008-02-14 23:33 ` Trond Myklebust
[not found] ` <20080214060201.GA17680@infradead.org>
[not found] ` <6599ad830802140722t2e3a2779sa323657dfd6da841@mail.gmail.com>
2008-02-14 15:23 ` Paul Menage [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=6599ad830802140723t2239c432v3610d9a0fd77e862@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).