David Woodhouse <dwmw2@infradead.org>:
> A good way to kill this myth, if myth it is, would be to set up a test
> suite, as I suggested before. You already have a 'randomconfig' for CML2, I
> believe? I think there's also one for CML1.
There is no randomconfig for CML2.
> Repeatedly make a random config (for a random architecture), with either
> CML1 or CML2. Make oldconfig with the other CML, then with the first again.
> If there are any differences between the original randomconfig output and
> the output after the two 'oldconfig' stages, you've hit something that may
> be a problem.
>
> Every time you hit such a difference, either fix it or document it and
> justify it. Ensure that the list of such justifications required is small,
> in order to improve the chance of CML2 being accepted.
This cycle is what I've been going through with a lot of my beta testers.
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a> - 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/
This archive was generated by hypermail 2b29 : Sat Feb 23 2002 - 21:00:11 EST