From: Garrett Kajmowicz <gkajmowi@tbaytel.net>
To: linux-kernel@vger.kernel.org
Cc: davej@codemonkey.org.uk
Subject: Re: [PATCH, TRIVIAL] 2.4.20-pre8 BeFS Config.in modification
Date: Tue, 1 Oct 2002 15:12:08 -0400 [thread overview]
Message-ID: <200210011512.08679.gkajmowi@tbaytel.net> (raw)
In-Reply-To: <20021001190648.GA24193@suse.de>
> 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
gkajmowi@tbaytel.net
prev parent reply other threads:[~2002-10-01 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 18:48 Garrett Kajmowicz
2002-10-01 19:06 ` Dave Jones
2002-10-01 19:12 ` Garrett Kajmowicz [this message]
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=200210011512.08679.gkajmowi@tbaytel.net \
--to=gkajmowi@tbaytel.net \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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®