From: "Eric S. Raymond" <esr@thyrsus.com>
To: Greg Banks <gnb@alphalink.com.au>
Cc: CML2 <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-devel] Why recovering from broken configs is too hard
Date: Thu, 3 May 2001 04:52:22 -0400 [thread overview]
Message-ID: <20010503045222.A28728@thyrsus.com> (raw)
In-Reply-To: <20010503034755.A27693@thyrsus.com> <3AF11A0D.FB206A2B@alphalink.com.au>
In-Reply-To: <3AF11A0D.FB206A2B@alphalink.com.au>; from gnb@alphalink.com.au on Thu, May 03, 2001 at 06:42:53PM +1000
Greg Banks <gnb@alphalink.com.au>:
> There is a natural order for presenting variables to the
> user, and that's the menu tree order. At least in the Linux
> kernel CML2 corpus the menus are roughly organised from most
> general to most specific options, so options appearing earlier
> in the tree are likely to appear in more constraints and you
> probably want to ask the user to mutate them later.
OK. Agreed, but it doesn't solve the general problem. Generating
models is still hard.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
To make inexpensive guns impossible to get is to say that you're
putting a money test on getting a gun. It's racism in its worst form.
-- Roy Innis, president of the Congress of Racial Equality (CORE), 1988
next prev parent reply other threads:[~2001-05-03 8:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 7:47 Why recovering from broken configs is too hard Eric S. Raymond
2001-05-03 8:03 ` Jeff Garzik
2001-05-03 8:09 ` Eric S. Raymond
2001-05-03 8:29 ` Alexander Viro
2001-05-03 8:42 ` [kbuild-devel] " Greg Banks
2001-05-03 8:52 ` Eric S. Raymond [this message]
2001-05-03 8:45 ` Ingo Oeser
2001-05-03 9:14 ` Alexander Viro
2001-05-03 9:43 ` Eric S. Raymond
2001-05-03 9:56 ` Alan Cox
2001-05-03 10:00 ` Alexander Viro
2001-05-03 15:55 ` Eric S. Raymond
2001-05-03 18:36 ` Alexander Viro
2001-05-03 14:54 ` David Mansfield
2001-05-03 15:58 ` Eric S. Raymond
2001-05-03 18:13 ` John Stoffel
2001-05-03 9:32 ` Eric S. Raymond
2001-05-03 10:15 ` [kbuild-devel] " Keith Owens
2001-05-03 16:59 ` Eric S. Raymond
2001-05-03 17:48 ` Alan Cox
2001-05-03 18:30 ` Eric S. Raymond
2001-05-03 18:41 ` Alan Cox
2001-05-03 19:03 ` Device driver from kernel2.2.x to kernel2.4 jalaja devi
2001-05-04 1:39 ` Andrew Morton
2001-05-03 22:58 ` [kbuild-devel] Why recovering from broken configs is too hard Keith Owens
2001-05-03 19:20 ` Michal Jaegermann
2001-05-03 23:58 ` Albert D. Cahalan
2001-05-03 22:55 ` David Lang
2001-05-04 7:47 ` [kbuild-devel] " Eric S. Raymond
-- strict thread matches above, loose matches on Subject: below --
2001-05-03 19:30 [kbuild-devel] " Wayne.Brown
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=20010503045222.A28728@thyrsus.com \
--to=esr@thyrsus.com \
--cc=gnb@alphalink.com.au \
--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