mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Joseph Fannin <jhf@rivenstone.net>
Cc: tytso@mit.edu, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [BK] 0/11  Ext2/3 Updates: Extended attributes, ACL, etc.
Date: Fri, 1 Nov 2002 12:56:20 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0211011239290.6949-100000@serv> (raw)
In-Reply-To: <20021101010607.GC1683@rivenstone.net>

Hi,

On Thu, 31 Oct 2002, Joseph Fannin wrote:

> > # Meta block cache for Extended Attributes (ext2/ext3)
> > config FS_MBCACHE
> >        tristate
> >        depends on EXT2_FS_XATTR || EXT3_FS_XATTR
> >        default m if EXT2_FS=m || EXT3_FS=m
> >        default y if EXT2_FS=y || EXT3_FS=y
> 
>     Okay, sorry for all the mails.
> 
>     "If multiple default statements are visible only the first is
> used."
> 
>     So the two default lines above need to be reversed.  This seems
> backwards to me (the last should be used), but I've said enough.

Well, I had to pick something and using the first is easier to implement, 
it's just different to cml1, which used the last definition.
BTW xconfig is a nice way to see how the config back end works, you can 
enable "Show All Options" and above entry will also be visible and you can 
watch how the value changes depending on the inputs.
BTW2 in the future above can be simplified into

config FS_MBCACHE
	tristate
	depends on EXT2_FS_XATTR || EXT3_FS_XATTR
	default EXT2_FS || EXT3_FS

bye, Roman


  reply	other threads:[~2002-11-01 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31  8:28 tytso
2002-11-01  0:24 ` Joseph Fannin
2002-11-01  0:47   ` Joseph Fannin
2002-11-01  1:06     ` Joseph Fannin
2002-11-01 11:56       ` Roman Zippel [this message]
2002-11-01 17:28         ` [PATCH] Fix 2.5-bk build error Joseph Fannin
2002-11-02  6:54           ` Theodore Ts'o
2002-11-02 11:53             ` Roman Zippel

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=Pine.LNX.4.44.0211011239290.6949-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=jhf@rivenstone.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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®