From: Joel Becker <Joel.Becker@oracle.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [Ocfs2-devel] [-mm patch] CONFIGFS_FS: "If unsure, say N."
Date: Wed, 29 Jun 2005 17:57:23 -0700 [thread overview]
Message-ID: <20050630005723.GE23823@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20050630004738.GA27478@stusta.de>
On Thu, Jun 30, 2005 at 02:47:38AM +0200, Adrian Bunk wrote:
> But I get your point, what about the patch below?
Non-descriptive. We are descriptive for sysfs (and even allow
the choice!). I'd say that leaving the description but perhaps adding
the caveat about modules and unsure-N might be a good way to go.
Joel
--
"If you are ever in doubt as to whether or not to kiss a pretty girl,
give her the benefit of the doubt"
-Thomas Carlyle
Joel Becker
Senior Member of Technical Staff
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2005-06-30 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 8:03 [-mm patch] CONFIGFS_FS shouldn't be user-visible Adrian Bunk
2005-06-29 21:30 ` Joel Becker
2005-06-30 0:47 ` [-mm patch] CONFIGFS_FS: "If unsure, say N." Adrian Bunk
2005-06-30 0:57 ` Joel Becker [this message]
2005-06-30 1:10 ` [Ocfs2-devel] " Adrian Bunk
2005-06-30 1:30 ` Joel Becker
2005-07-02 10:58 ` Adrian Bunk
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=20050630005723.GE23823@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox