From: Al Viro <viro@ZenIV.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
akpm@linux-foundation.org, hch@infradead.org, serue@us.ibm.com,
haveblue@us.ibm.com, linuxram@us.ibm.com,
linux-fsdevel@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: git tree with VFS stuff
Date: Wed, 20 Feb 2008 14:29:37 +0000 [thread overview]
Message-ID: <20080220142937.GX27894@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20080221011348.ef5da6c5.sfr@canb.auug.org.au>
On Thu, Feb 21, 2008 at 01:13:48AM +1100, Stephen Rothwell wrote:
> Hi Miklos,
>
> On Tue, 19 Feb 2008 14:32:28 +0100 Miklos Szeredi <miklos@szeredi.hu> wrote:
> >
> > I've created a git tree with the following mounts related stuff:
> >
> > - read-only bind mounts
> > - /proc/<pid>/mountinfo
> > - unprivileged mounts
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfsstuff.git master
> >
> > I guess, giving these a spin in linux-next wouldn't hurt?
>
> I don't think this is what we want to use linux-next for. Linux-next is
> really a place for stuff that will pretty clearly go into the next kernel
> release i.e. 2.6.26 right now. If you want to experiment on things for
> beyond that timeframe, then a snapshot of linux-next may be a good base.
> I will take them when they reach the appropriate subsystem tree and are
> ready for integration.
FWIW, I must apologize for delay with getting the damn tree open on
kernel.org ;-/ The last couple of weeks had been Not Fun(tm) in a
lot of respects.
Hopefully I'll finish putting the damn thing into publishable shape by
tomorrow. As for the stuff mentioned above... ro-bind series - definitely
yes, mountinfo - IMO needs a sane discussion of what and how should be shown
wrt propagation state, unprivileged mounts - in the "need to finish reviewing"
pile.
prev parent reply other threads:[~2008-02-20 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 13:32 git tree with VFS stuff Miklos Szeredi
2008-02-20 14:13 ` Stephen Rothwell
2008-02-20 14:29 ` Al Viro [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=20080220142937.GX27894@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=miklos@szeredi.hu \
--cc=serue@us.ibm.com \
--cc=sfr@canb.auug.org.au \
/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).