From: Joshua Kwan <joshk@triplehelix.org>
To: Christopher Sawtell <csawtell@paradise.net.nz>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: bug in -test11 make xconfig
Date: Sat, 29 Nov 2003 03:25:49 -0800 [thread overview]
Message-ID: <20031129112549.GD15782@triplehelix.org> (raw)
In-Reply-To: <200311292325.44935.csawtell@paradise.net.nz>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Sat, Nov 29, 2003 at 11:25:44PM +1300, Christopher Sawtell wrote:
> I have noticed that it is not possible to configure the kernel to use the
> xfs file system using the 'make xconfig' command.
> 'make menuconfig' and 'make gconfig' appear to work correctly.
I assume this is a 2.5 or 2.6 kernel source you are talking about,
since gconfig is unavailable in 2.4. Could you be more precise?
With 2.6.0-test11 I'm able to enable XFS support through xconfig.
> No need to reply, & I'm not worth to be be subscribed because of insufficient> knowledge.
If you didn't want anyone to reply you wouldn't have posted this message
to begin with.
And sometimes it's a curse to be subscribed to linux-kernel. There's
lots to read all the time. :)
--
Joshua Kwan
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2003-11-29 11:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 10:25 bug in -test11 make xconfig Christopher Sawtell
2003-11-29 11:18 ` NForce2 pseudoscience stability testing (2.6.0-test11) Craig Bradney
2003-11-29 16:34 ` Julien Oster
2003-11-29 16:47 ` Craig Bradney
2003-11-29 16:54 ` Craig Bradney
2003-12-07 11:32 ` Jussi Laako
2003-12-07 15:49 ` Prakash K. Cheemplavam
2003-12-01 18:30 ` Pavel Machek
2003-12-01 20:20 ` Craig Bradney
2003-11-29 11:25 ` Joshua Kwan [this message]
2003-11-29 12:00 ` bug in -test11 make xconfig Andre Tomt
2003-11-29 14:39 ` Roman Zippel
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=20031129112549.GD15782@triplehelix.org \
--to=joshk@triplehelix.org \
--cc=csawtell@paradise.net.nz \
--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;
as well as URLs for NNTP newsgroup(s).