From: Nicolas Pitre <nico@cam.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: <esr@thyrsus.com>, <linux-kernel@vger.kernel.org>,
<kbuild-devel@lists.sourceforge.net>
Subject: Re: CML2 1.0.0 doesn't remember configuration changes
Date: Sat, 14 Apr 2001 00:33:34 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0104140032150.24402-100000@xanadu.home> (raw)
In-Reply-To: <3AD7B619.D1A812CC@mandrakesoft.com>
On Fri, 13 Apr 2001, Jeff Garzik wrote:
> "Eric S. Raymond" wrote:
> > OK, 1.1.0 will do these things. I'm still not certain I have `make
> > oldconfig' right, but I trust someone will club me gently over the
> > head if it's still not up to spec.
>
> Yep :) 'vi .config' + 'make oldconfig' is the most efficient way to
> update your kernel config, if you really know what you are doing.
I thought I was the only one to do that! =-)
Nicolas
next prev parent reply other threads:[~2001-04-14 5:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 10:47 CML2 1.0.0 release announcement Eric S. Raymond
2001-04-10 12:14 ` Russell King
2001-04-11 19:43 ` davej
2001-04-11 20:04 ` Christoph Hellwig
2001-04-11 20:16 ` Dave Jones
2001-04-11 20:27 ` Christoph Hellwig
2001-04-11 22:23 ` Alan Cox
2001-04-11 23:19 ` esr
2001-04-11 23:30 ` Alan Cox
2001-04-11 23:33 ` Alan Cox
2001-04-12 0:45 ` esr
[not found] ` <3AD4FC54.C86AACBE@mandrakesoft.com>
2001-04-12 1:28 ` esr
2001-04-12 1:43 ` CML2 1.0.0 doesn't remember configuration changes jeff millar
2001-04-12 2:50 ` esr
2001-04-12 5:35 ` jeff millar
2001-04-12 2:06 ` esr
2001-04-12 21:20 ` Ingo Oeser
2001-04-14 2:11 ` Eric S. Raymond
2001-04-14 2:29 ` Jeff Garzik
2001-04-14 4:33 ` Nicolas Pitre [this message]
2001-04-12 10:45 ` CML2 1.0.0 release announcement Alan Cox
2001-04-11 22:20 ` esr
2001-04-12 7:09 ` Albert D. Cahalan
2001-04-12 8:57 ` Jamie Lokier
2001-04-12 10:57 ` esr
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=Pine.LNX.4.33.0104140032150.24402-100000@xanadu.home \
--to=nico@cam.org \
--cc=esr@thyrsus.com \
--cc=jgarzik@mandrakesoft.com \
--cc=kbuild-devel@lists.sourceforge.net \
--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).