linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@caldera.de>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net,
	"Eric S. Raymond" <esr@snark.thyrsus.com>
Subject: Re: CML2 1.0.0 release announcement
Date: Wed, 11 Apr 2001 22:27:22 +0200	[thread overview]
Message-ID: <20010411222722.A31359@caldera.de> (raw)
In-Reply-To: <200104112004.WAA30164@ns.caldera.de> <Pine.LNX.4.30.0104112212310.29627-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.30.0104112212310.29627-100000@Appserv.suse.de>; from davej@suse.de on Wed, Apr 11, 2001 at 10:16:36PM +0200

On Wed, Apr 11, 2001 at 10:16:36PM +0200, Dave Jones wrote:
> On Wed, 11 Apr 2001, Christoph Hellwig wrote:
> 
> > > CML2 takes around 15 seconds before I get that far.
> > > This is on an Athlon 800 w/512MB. I dread to think how this
> > > responds on a 486.
> >
> > If you look for something _even_ faster try mconfig.  For everyone who is
> > interested, I've put my latests half-way stable version is on ftp.  It's at
> >   ftp.openlinux.org:/pub/people/hch/mconfig/mconfig-0.19-pre1.tar.gz
> > Props for all the hard work go to Michael Elizabeth Chastain!
> 
> This is the first I've heard of mconfig. (I don't track the kbuild list)
> Does it solve all the problems that Eric's solution proposes?
> It's certainly fast (CML1 menuconfig speed at least).

Not all (yet).
o It is one programm with multiple frontends:
	old,
	text,
	ncurses,
	random,
	maximum,
	minimum,
	syntax checking
	(X is still missing as my brain is not made for GUI programming)

o An 'show me all options and handle the rest' mode is still missing -
  my devel tree has something like that in the works, but I'll probably
  never finish it now that CML2 is official.

o it still has multiple top-level config.in.  Again that is easily fixable
  and in fact I did a patch for it (including {old,menu,x}config support
  in 2.3 times but never submitted it.

Something missing?

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.

  reply	other threads:[~2001-04-11 20:27 UTC|newest]

Thread overview: 26+ 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 [this message]
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
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
     [not found] <fa.i13tmhv.9kga3t@ifi.uio.no>
     [not found] ` <fa.g0offov.1jmmkh9@ifi.uio.no>
2001-04-12  8:50   ` Giacomo Catenazzi

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=20010411222722.A31359@caldera.de \
    --to=hch@caldera.de \
    --cc=davej@suse.de \
    --cc=esr@snark.thyrsus.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).