The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dave Hansen <hansendc@us.ibm.com>
To: Ian Kent <raven@themaw.net>
Cc: Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	haveblue@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: Read-only bind mount patches
Date: Mon, 14 May 2007 09:01:20 -0700	[thread overview]
Message-ID: <1179158480.366.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1179158131.3811.59.camel@raven.themaw.net>

On Mon, 2007-05-14 at 23:55 +0800, Ian Kent wrote:
> 
> Anything I can do to help?
> If so maybe we could reduce the time to posting a bit.

Probably nothing to actually speed up the development, but I'd really
appreciate some testing once I do post them.  How about I send you an
advance copy, or cc you on the RFC?

-- Dave


  reply	other threads:[~2007-05-14 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14 13:22 Read-only bind mount patches Ian Kent
2007-05-14 15:10 ` Dave Hansen
2007-05-14 15:55   ` Ian Kent
2007-05-14 16:01     ` Dave Hansen [this message]
2007-05-14 16:29       ` Ian Kent

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=1179158480.366.8.camel@localhost.localdomain \
    --to=hansendc@us.ibm.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=haveblue@linux.vnet.ibm.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raven@themaw.net \
    /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