OK, I obviously don't expect the behaviour to be _exactly_ identical. If
CML2 allows the authors' intent to be more closely adhered to, that's a good
thing. But if the CML2 files exhibit behaviour which was clearly _not_ the
intention of the original CML1, that is a change which should be made under
separate cover.
> Such as what? Do you have any examples here?
The MAC/SCSI dependencies, which it seems were 'simplified' at the cost of
preventing certain combinations which were unlikely but valid, and which it
was possible to select with the original rules.
Also of course the whole class of dependencies which people are talking
about introducing for the benefit of the hypothetical Aunt Tillie.
I don't know how many, if any, of this kind of changes are _actually_ made
in the current CML2 rules files - what I'm saying is that there _should_ be
none. Such large changes to the policy are entirely unrelated to CML2
itself, and should be discussed separately.
If your response to this is "But there are no such changes, you
misunderstood the MAC/SCSI dependency conversation and the Aunt Tillie stuff
was all hypothetical, what are you talking about?", then good - that's
precisely the answer I was after.
All I'm asking for is a clear agreement that within reason, the behaviour
of the CML2 rules files immediately after CML2 is merged will match the
intended behaviour of the CML1 rules prior to the merge.
-- dwmw2
- 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/