mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: Pavel Machek <pavel@suse.cz>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: GFS2 Filesystem [13/16]
Date: Mon, 27 Feb 2006 08:58:58 +0000	[thread overview]
Message-ID: <1141030738.6400.788.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <20060224223046.GS8083@ca-server1.us.oracle.com>

Hi,

On Fri, 2006-02-24 at 14:30 -0800, Joel Becker wrote:
> On Wed, Feb 22, 2006 at 06:50:59PM +0000, Pavel Machek wrote:
> > > --- a/fs/Kconfig
> > > +++ b/fs/Kconfig
> > > @@ -883,8 +884,6 @@ config CONFIGFS_FS
> > >  	  Both sysfs and configfs can and should exist together on the
> > >  	  same system. One is not a replacement for the other.
> > >  
> > > -	  If unsure, say N.
> > > -
> > 
> > Why? Most users probably still want configfs_fs=N.
> 
> 	What version is this patch against?  This line was removed from
> mainline a while ago.
> 	As to why it was removed, the discussion happened back then.
> Basically, if something requires CONFIGFS_FS (eg, OCFS2) and is a
> module, then a user is asked whether they want configfs as a module or
> built-in.  Text saying "say N" is completely incorrect there.
> 
> Joel
> 
Checking the gfs2 git tree and Linus' tree again reveals that its not
something that we changed. I think I must have fed the wrong command to
git to produce the diff as the change is quite clearly there, exactly
same in both trees,

Steve.



  reply	other threads:[~2006-02-27  8:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 15:05 Steven Whitehouse
2006-02-22 18:50 ` Pavel Machek
2006-02-24 22:30   ` Joel Becker
2006-02-27  8:58     ` Steven Whitehouse [this message]
2006-02-27  8:46   ` Steven Whitehouse

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=1141030738.6400.788.camel@quoit.chygwyn.com \
    --to=swhiteho@redhat.com \
    --cc=Joel.Becker@oracle.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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®