All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Michael Halcrow <mike@halcrow.us>
Cc: linux-fsdevel@vger.kernel.org,
	Phillip Hellewell <phillip@hellewell.homeip.net>,
	yoder1@us.ibm.com, mcthomps@us.ibm.com, emilyr@us.ibm.com
Subject: Re: eCryptfs: Request for review
Date: Tue, 18 Oct 2005 12:59:02 -0700	[thread overview]
Message-ID: <20051018195901.GA31368@kroah.com> (raw)
In-Reply-To: <20051018193811.GA11545@halcrow.us>

On Tue, Oct 18, 2005 at 02:38:11PM -0500, Michael Halcrow wrote:
> We are preparing to send eCryptfs to the LKML for inclusion in the -mm
> tree, and we would like to solicit feedback from those in the
> community who have an interest in Linux filesystems and cryptographic
> applications. We are mainly interested at this point in comments that
> might help us with VFS-related issues.

Then please post patches in the proper form.  Pointing to a cvs server
just doesn't cut it :)

thanks,

greg k-h

  reply	other threads:[~2005-10-18 19:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18 19:38 eCryptfs: Request for review Michael Halcrow
2005-10-18 19:59 ` Greg KH [this message]
2005-10-19 15:36 ` Charles P. Wright
2005-10-19 19:00   ` Michael Thompson
2005-10-19 19:38     ` Charles P. Wright
2005-10-19 19:55       ` Michael Thompson
2005-10-19 21:02         ` Erez Zadok
2005-10-19 21:38         ` Badari Pulavarty
2005-10-21 21:44           ` Michael Thompson
2005-10-21 21:56             ` Shaya Potter
2005-10-21 22:49             ` Badari Pulavarty
2005-10-24 18:19               ` Michael Thompson
2005-10-26 20:05                 ` Michael Thompson
2005-10-26 20:13                   ` Anton Altaparmakov
2005-10-27 13:13                     ` Charles P. Wright
2005-10-20 14:25         ` Charles P. Wright
2005-10-26 23:29   ` Michael Thompson
2005-10-27 13:12     ` Charles P. Wright

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=20051018195901.GA31368@kroah.com \
    --to=greg@kroah.com \
    --cc=emilyr@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mcthomps@us.ibm.com \
    --cc=mike@halcrow.us \
    --cc=phillip@hellewell.homeip.net \
    --cc=yoder1@us.ibm.com \
    /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.