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
[email protected]
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
> If those filesystems had a dozen options each, it'd be worthwhile
> perhaps. Saving 1-2 lines per-fs for the whole fs/Config.in
> makes this seem not-so-worthwhile imo, but others may think otherwise..
>
> Dave
I am not doing this to reduce the size of the Config.in files. I am doing it
because my main project (writing a script to provide stripped-down versions
of the Linux kernel source code for people over slower connections) all but
requires everything neat and in it's own directory for optimal performance.
I could use a lot of grep/gawk but that would cause more problems for people
who wanted to download the stripped source code.
Besides, it's The Right Thing To Do {tm}
Please Cc any comments to:
Garrett Kajmowicz
[email protected]
On Tue, Oct 01, 2002 at 02:48:06PM -0400, Garrett Kajmowicz wrote:
> 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?
If those filesystems had a dozen options each, it'd be worthwhile
perhaps. Saving 1-2 lines per-fs for the whole fs/Config.in
makes this seem not-so-worthwhile imo, but others may think otherwise..
Dave
--
| Dave Jones. http://www.codemonkey.org.uk