From: Garrett Kajmowicz <gkajmowi@tbaytel.net>
To: linux-kernel@vger.kernel.org
Cc: will@cs.earlham.edu
Subject: [PATCH, TRIVIAL] 2.4.20-pre8 BeFS Config.in modification
Date: Tue, 1 Oct 2002 14:48:06 -0400 [thread overview]
Message-ID: <200210011448.06125.gkajmowi@tbaytel.net> (raw)
I am planning on making an effort to move the relevent code for the Config.in
files into the appropriate directory. Attached is a simple patch which will
do this for the BeFS.
Questions:
Is this appropriate for this list?
Are there any reasons not to do this?
As I am planning on doing a lot of these, where should I send them?
Any other suggestions/advice?
Please Cc: all comments to:
Garrett Kajmowicz
gkajmowi@tbaytel.net
diff -Nru linux-2.4.19old/fs/Config.in linux-2.4.19new/fs/Config.in
--- linux-2.4.19old/fs/Config.in 2002-10-01 08:22:21.000000000 -0400
+++ linux-2.4.19new/fs/Config.in 2002-10-01 14:11:39.000000000 -0400
@@ -19,8 +19,7 @@
dep_tristate 'Apple Macintosh file system support (EXPERIMENTAL)'
CONFIG_HFS_FS $CONFIG_EXPERIMENTAL
-dep_tristate 'BeOS file systemv(BeFS) support (read only) (EXPERIMENTAL)'
CONFIG_BEFS_FS $CONFIG_EXPERIMENTAL
-dep_mbool ' Debug Befs' CONFIG_BEFS_DEBUG $CONFIG_BEFS_FS
+source fs/befs/Config.in
dep_tristate 'BFS file system support (EXPERIMENTAL)' CONFIG_BFS_FS
$CONFIG_EXPERIMENTAL
diff -Nru linux-2.4.19old/fs/befs/Config.in linux-2.4.19new/fs/befs/Config.in
--- linux-2.4.19old/fs/befs/Config.in 1969-12-31 19:00:00.000000000 -0500
+++ linux-2.4.19new/fs/befs/Config.in 2002-10-01 14:10:54.000000000 -0400
@@ -0,0 +1,2 @@
+dep_tristate 'BeOS file systemv(BeFS) support (read only) (EXPERIMENTAL)'
CONFIG_BEFS_FS $CONFIG_EXPERIMENTAL
+dep_mbool ' Debug Befs' CONFIG_BEFS_DEBUG $CONFIG_BEFS_FS
next reply other threads:[~2002-10-01 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 18:48 Garrett Kajmowicz [this message]
2002-10-01 19:06 ` Dave Jones
2002-10-01 19:12 ` Garrett Kajmowicz
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=200210011448.06125.gkajmowi@tbaytel.net \
--to=gkajmowi@tbaytel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=will@cs.earlham.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®