public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giacomo Catenazzi <cate@dplanet.ch>
To: David Lang <david.lang@digitalinsight.com>
Cc: Giacomo Catenazzi <cate@debian.org>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	andersen@codepoet.org, Roman Zippel <zippel@linux-m68k.org>,
	linux-kernel@vger.kernel.org
Subject: Re: linux kernel config converter
Date: Thu, 21 Feb 2002 16:05:01 +0100	[thread overview]
Message-ID: <3C750C9D.7090607@dplanet.ch> (raw)
In-Reply-To: <Pine.LNX.4.44.0202210655020.8696-100000@dlang.diginsite.com>



David Lang wrote:

>>David Lang wrote:
>>
>>>2. does it handle the 'I want this feature, turn on everything I need for
>>>it'?
>>>
>>>3. if it handles #2 what does it do if you turn off that feature again
>>>(CML2 turns off anything it turned on to support that feature, assuming
>>>nothing else needs it)
> 
> #3 may be, but #2 isn't possible if the language doesn't provide enough
> info for the tool to know what is needed to make a feature work.


Ok. I agree, #2 is also a configuration language item.
(actual CML doesn't support #2).

It seems that actual language support #2:
you see that every symbol have a list of dependencies,
so a configuration tools can change these dependencies.

But also CML2 don't support #2 for strange/complex rules (<1%).
(It complains about unmet dependencies.) and we should
not support it for such rules (i.e. if a rules conflicts
with PCI or other rules that force BIG changes...).


	giacomo



  reply	other threads:[~2002-02-21 15:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.fsgrt4v.1bngh9t@ifi.uio.no>
     [not found] ` <fa.hp69onv.i7qtq3@ifi.uio.no>
2002-02-21 14:06   ` linux kernel config converter Giacomo Catenazzi
2002-02-21 14:26     ` Jeff Garzik
2002-02-21 14:39       ` Giacomo Catenazzi
2002-02-21 15:11         ` Jeff Garzik
2002-02-21 16:00       ` Randy.Dunlap
     [not found]   ` <fa.lqt3hav.190o1i9@ifi.uio.no>
2002-02-21 14:50     ` Giacomo Catenazzi
2002-02-21 14:56       ` David Lang
2002-02-21 15:05         ` Giacomo Catenazzi [this message]
     [not found] <fa.gq2s5iv.1s4in@ifi.uio.no>
2002-02-21 13:28 ` Giacomo Catenazzi
2002-02-21 14:11   ` Roman Zippel
2002-02-21 14:32     ` Giacomo Catenazzi
2002-02-21 15:19       ` Roman Zippel
2002-02-21 10:48 Roman Zippel
2002-02-21 11:40 ` Jeff Garzik
2002-02-21 12:21   ` Roman Zippel
2002-02-21 12:32     ` Jeff Garzik
2002-02-21 12:54 ` Erik Andersen
2002-02-21 13:21   ` Jeff Garzik
2002-02-21 14:28     ` David Lang
2002-02-21 14:36       ` Jeff Garzik
2002-02-21 14:40         ` David Lang
2002-02-21 15:05           ` Jeff Garzik
2002-02-21 15:41             ` Jason Lunz
2002-02-21 15:54               ` Jeff Garzik
2002-02-21 15:18         ` Alan Cox
2002-02-21 15:08           ` Jeff Garzik
2002-02-21 15:22             ` Gerd Knorr
2002-02-21 15:33       ` Roman Zippel
2002-02-21 18:53     ` Andreas Dilger

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=3C750C9D.7090607@dplanet.ch \
    --to=cate@dplanet.ch \
    --cc=andersen@codepoet.org \
    --cc=cate@debian.org \
    --cc=david.lang@digitalinsight.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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