public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sgi.com>
To: xfs-masters@oss.sgi.com
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
	nathans@sgi.com, linux-xfs@oss.sgi.com,
	linux-kernel@vger.kernel.org
Subject: Re: [xfs-masters] Re: [PATCH] pull XFS support out of Kconfig submenu
Date: Thu, 18 Aug 2005 10:23:02 -0500	[thread overview]
Message-ID: <4304A7D6.3000307@sgi.com> (raw)
In-Reply-To: <20050818135356.GA16845@taniwha.stupidest.org>

Chris Wedgwood wrote:
> On Wed, Aug 17, 2005 at 10:45:48PM +0200, Jesper Juhl wrote:
> 
> 
>>It seems slightly odd to me that XFS support should be in a separate
>>submenu, when all the other filesystems are not using submenus but
>>are directly selectable from the Filesystems menu.
> 
> 
> XFS also has an out-of-tree version.  Making it a submenu is probably
> to make maintenance easier (ie. replace files, not merge).
> 

Where the Kconfig is vs. where the menu appears are 2 different things 
though.  The latest kernel has our own Kconfig in fs/xfs, and fs/Kconfig 
just does:

source "fs/xfs/Kconfig"

This does facilitate swapping in a devel version of fs/xfs via a 
symlink, etc.

However, fs/xfs/Kconfig does still start with

menu "XFS support"

which puts it in a submenu, unlike every other fs.

I have no problem with removing the submenu.

-Eric

  parent reply	other threads:[~2005-08-18 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17 20:45 [PATCH] pull XFS support out of Kconfig submenu Jesper Juhl
2005-08-18 13:53 ` Chris Wedgwood
2005-08-18 15:22   ` [xfs-masters] " Russell Cattelan
2005-08-18 22:55     ` Nathan Scott
2005-08-18 15:23   ` Eric Sandeen [this message]
2005-08-18 15:32     ` Eric Sandeen

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=4304A7D6.3000307@sgi.com \
    --to=sandeen@sgi.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=nathans@sgi.com \
    --cc=xfs-masters@oss.sgi.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