From: Andrew Morton <akpm@osdl.org>
To: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00 of 23][-mm] Unionfs: Stackable Namespace Unification Filesystem
Date: Thu, 12 Oct 2006 13:54:28 -0700 [thread overview]
Message-ID: <20061012135428.024d0d33.akpm@osdl.org> (raw)
In-Reply-To: <patchbomb.1160633917@thor.fsl.cs.sunysb.edu>
On Thu, 12 Oct 2006 02:18:37 -0400
Josef "Jeff" Sipek <jsipek@cs.sunysb.edu> wrote:
> This set of patches constitutes Unionfs version 2.0.
So we need to get this reviewed.
Christoph and I are pretty much the only people who do filesystem
reviewing, despite the fact that we have hoards of filesystem developers
out there busily doing their own stuff (and that includes the unionfs
developers, I might add).
Our review-to-development ratio is wildly out of whack and I don't know how
to fix that.
Meanwhile, from a quick scan I'd say that unionfs is much, much too lightly
commented for a review to be particularly effective. Please work on that.
next parent reply other threads:[~2006-10-12 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <patchbomb.1160633917@thor.fsl.cs.sunysb.edu>
2006-10-12 20:54 ` Andrew Morton [this message]
2006-10-13 6:54 ` Pekka Enberg
2006-10-13 13:41 ` Jan Engelhardt
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=20061012135428.024d0d33.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jsipek@cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®