lkml.org 
[lkml]   [2001]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Requirement of make oldconfig [was: Re: [kbuild-devel] Re: CML2 1.3.1, aka ...]
Date
From
> Horst von Brand <vonbrand@inf.utfsm.cl>:
> > If you support broken configurations in any way, your program is just
> > wildly guessing what they did mean. The exact (and very probably not in any
> > way cleanly thought out) behaviour in corner cases then becomes "the way
> > things work", and we end up in an unmaintainable mess yet again.
>
> Yes, this is precisely what I fear.

I have been thinking about this in more detail. In a sense oldconfig does do
stuff you dont see and can cause suprises but its better than 'fix it yourself
tough' which is the other approach.

If that aspect of it worries you collect a list of the symbols that were
changed by the oldconfig process and colour them differently and/or offer
a view of them as part of the navigation

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:52    [W:0.068 / U:4.220 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site