[lkml]   [2001]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: CML2 design philosophy heads-up
>>>>> "Eric" == Eric S Raymond <> writes:

Eric> Jes Sorensen <>:
Eric> # These were separate questions in CML1 derive MAC_SCC from MAC
Eric> & SERIAL derive MAC_SCSI from MAC & SCSI derive SUN3_SCSI from
Eric> (SUN3 | SUN3X) & SCSI
>> As Alan already pointed out thats assumption is invalid.

Eric> I'm in touch with Ray Knight directly and will fix this as he
Eric> requests.

If Ray wants to fix things, it's just fine with me.

>> Yes I have objections. I thought I had made this clear a long time
>> ago: Go play with another port and leave the m68k port alone.

Eric> Does this mean you'll take over maintaining the CML2 rules files
Eric> for the m68k port, so I don't have to? That would be wonderful.

For a start, so far there has been no reason whatsoever to change the
format of definitions.

Eric> Reasoned objections can change my behavior. Grunting
Eric> territorial challenges at me will not. You have two options:
Eric> (1) persuade Linus that the whole CML2 thing is a bad idea and
Eric> should be dropped, or (2) work with me to correct any errors I
Eric> have made and improve the system. Growling at me and hoping I
Eric> go away won't work, not when I've invested a year's effort in
Eric> this project.

So far you have only been irritating developers for no reason. What I
asked you to do is to NOT change whatever config options developers
developers felt were necessary to introduce. If you want to change the
format of the files go ahead. Messing around with the config
options themselves is *not* for you to do, nor are you to impose a
more restrictive space for people to work in.

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.357 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site