[lkml]   [2001]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Brown-paper-bag bug in m68k, sparc, and sparc64 config files
On 19 May 2001 21:06:51 -0400, Benedict Bridgwater wrote:
> > This bug unconditionally disables a configuration question -- and it's
> > so old that it has propagated across three port files, without either
> > of the people who did the cut and paste for the latter two noticing it.
> >
> > This sort of thing would never ship in CML2, because the compiler
> > would throw an undefined-symbol warning on BLK_DEV_ST. The temptation
> > to engage in sarcastic commentary at the expense of people who still
> > think CML2 is an unnecessary pain in the butt is great. But I will
> > restrain myself. This time.
> So a shortcoming of the CML1 tools justifies the CML2 language?
> I guess the next bug found in the Python2 interpreter will justify
> writing CML3 in FORTRAN.

IIRC, Eric floated the CML2 idea over a year ago, provided some
rudimentary code and requested feedback. There has seemed, for a long
time, to be agreement amoungst most kernel developers that there were
serious problems with CML1 and that it needed to be junked. There are
many things that CML1 was not going to allow us to do that will be
possible with CML2 (subsetting of the code tree, etc). I don't think
Eric's statement about this particular brown-paper-bag bug means that he
thinks that this alone justifies migrating to CML2. There are a lot of
good reasons for the migration. It isn't, perhaps, a perfect solution,
but it is one that Eric has implemented with a year's worth of effort,
with full knowledge of the kernel development community and with an open
invitation for contributions and feedback. To rag on it now seems
belated and unhelpful. It would be more useful if you helped Eric
improve CML2, since there appears to be agreement that it will be used
in 2.5.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

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