On Sun, Aug 15, 2004 at 09:37:30PM +0200, Geert Uytterhoeven wrote:
On Sun, 15 Aug 2004, Roman Zippel wrote:
On Sat, 14 Aug 2004, Adrian Bunk wrote:
This is less a problem, as here it's clear that you want a boolean result,
but something like FOO=n is really a string compare and FOO
On Mon, Aug 16, 2004 at 01:01:35AM +0200, Roman Zippel wrote:
Hi,
Hi Roman,
On Sun, 15 Aug 2004, Geert Uytterhoeven wrote:
What about normal numbers? I don't think requiring quotes everywhere for
this is a good idea.
And numbers (both decimal and hex) can easily be distinguished
On Wed, Aug 11, 2004 at 10:17:25PM +0200, Adrian Bunk wrote:
On Sat, Aug 07, 2004 at 08:12:56PM +0200, Arnd Bergmann wrote:
...
On Samstag, 7. August 2004 19:25, Adrian Bunk wrote:
Is there eny reason for such options that are never visible nor enabled,
or could they be removed?
On Wed, Aug 11, 2004 at 11:40:32PM +0200, Sam Ravnborg wrote:
Roman, a related Q.
Why not error out, or at least warn when encountering an unknow
symbol in a 'depends on' statement?
...
That doesn't sound like a good idea, consider e.g.:
config BAGETLANCE
tristate Baget AMD LANCE
On Thu, 12 Aug 2004 02:18:48 +0200 Adrian Bunk wrote:
| On Wed, Aug 11, 2004 at 11:45:21PM +0200, Roman Zippel wrote:
|
| Hi,
|
| Hi Roman,
|
| On Wed, 11 Aug 2004, Adrian Bunk wrote:
|
| Roman, is it intentional that PCMCIA!=n is true if there's no PCMCIA
| option, or is it simply a
