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