linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: linux-kernel@vger.kernel.org
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: [PATCH] 2.4.20-pre8 - Config.in: Second extended fs rename / move Ext3 to a wiser place
Date: Thu, 26 Sep 2002 21:44:38 +0200	[thread overview]
Message-ID: <200209261941.34278.m.c.p@wolk-project.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 567 bytes --]

Hi there,

these are just cosmetic fixes.

I think we can do the following:

1. rename: "Second extended fs support" to "Ext2 file system support"
    (to be equal to Ext3fs)

2. move: "Ext3 journalling file system support" near under to Ext2 fs.

Coments?


Marcello, if ok, please apply.

-- 
Kind regards
        Marc-Christian Petersen

http://sourceforge.net/projects/wolk

PGP/GnuPG Key: 1024D/569DE2E3DB441A16
Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16
Key available at www.keyserver.net. Encrypted e-mail preferred.

[-- Attachment #2: 2.4_1-ext2-rename.patch --]
[-- Type: text/x-diff, Size: 372 bytes --]

--- linux-2.4-old/fs/Config.in		Thu Sep 26 12:19:14 2002
+++ linux-2.4-new/fs/Config.in		Thu Sep 26 19:26:31 2002
@@ -83,7 +83,7 @@
 
 tristate 'ROM file system support' CONFIG_ROMFS_FS
 
-tristate 'Second extended fs support' CONFIG_EXT2_FS
+tristate 'Ext2 file system support' CONFIG_EXT2_FS
 
 tristate 'System V/Xenix/V7/Coherent file system support' CONFIG_SYSV_FS
 

[-- Attachment #3: 2.4_2-ext3-move-right-place.patch --]
[-- Type: text/x-diff, Size: 1402 bytes --]

--- linux-2.4-old/fs/Config.in		Thu Sep 26 12:19:14 2002
+++ linux-2.4-new/fs/Config.in		Thu Sep 26 19:26:31 2002
@@ -24,12 +24,7 @@
 
 dep_tristate 'BFS file system support (EXPERIMENTAL)' CONFIG_BFS_FS $CONFIG_EXPERIMENTAL
 
-tristate 'Ext3 journalling file system support' CONFIG_EXT3_FS
-# CONFIG_JBD could be its own option (even modular), but until there are
-# other users than ext3, we will simply make it be the same as CONFIG_EXT3_FS
-# dep_tristate '  Journal Block Device support (JBD for ext3)' CONFIG_JBD $CONFIG_EXT3_FS
-define_bool CONFIG_JBD $CONFIG_EXT3_FS
-dep_mbool '  JBD (ext3) debugging support' CONFIG_JBD_DEBUG $CONFIG_JBD
+# old ext3fs config place. Moved near to ext2fs
 
 # msdos file systems
 tristate 'DOS FAT fs support' CONFIG_FAT_FS
@@ -85,6 +85,13 @@
 
 tristate 'Ext2 file system support' CONFIG_EXT2_FS
 
+tristate 'Ext3 journalling file system support' CONFIG_EXT3_FS
+# CONFIG_JBD could be its own option (even modular), but until there are
+# other users than ext3, we will simply make it be the same as CONFIG_EXT3_FS
+# dep_tristate '  Journal Block Device support (JBD for ext3)' CONFIG_JBD $CONFIG_EXT3_FS
+define_bool CONFIG_JBD $CONFIG_EXT3_FS
+dep_mbool '  JBD (ext3) debugging support' CONFIG_JBD_DEBUG $CONFIG_JBD
+
 tristate 'System V/Xenix/V7/Coherent file system support' CONFIG_SYSV_FS
 
 tristate 'UDF file system support (read only)' CONFIG_UDF_FS

                 reply	other threads:[~2002-09-26 20:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200209261941.34278.m.c.p@wolk-project.de \
    --to=m.c.p@wolk-project.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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;
as well as URLs for NNTP newsgroup(s).