I have said before; I am *not* going to make KB vs. KiB a
metaconfiguration option -- that would defeat the whole purpose of
having standard terminology. That decision is final, and this subject
The other is not a bad idea in principle. I've thought before about
adding a feature that would add specified boilerplate to the help a
tristate symbol, for exactly the reasons you suggest. Three things make
it a bit messy in practice.
One is that it would have to be expressed in the rulebase, ruther than
wired into the code. I will not hardwire specific knowledge about
the Linux-specific properties of tristate symbols into the CML2 engine.
CML2 is already being used by at least two projects other than the kernel
and I know of a third that has it under consideration. Therefore I must
preserve its generality.
The second problem is that the module boilerplate is not all
boilerplate. Most instances contain the name of the generated module
object file. Thus, ypo do this right, I would have to declare module
names in the rulebase, one for each tristate entry. This implies a
significant extension to the CML2 language, which I'm reluctant to do
right now. The design is stable. I want it to stay that way until
(at least) well after CML2 achieves acceptance.
Third, I don't want to do major surgery on Configure.help until after
CML2 enters the tree. Were I to do so, I would then have to maintain
two different versions of Configure.help. That would be too big a pain.
Therefore, I'm going to defer consideration of this feature for now.
I certainly will not consider it until after CML2 goes into the 2.5 tree,
and may not consider it until there is some kind of final decision on
a 2.4 backport.
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
When only cops have guns, it's called a "police state". -- Claire Wolfe, "101 Things To Do Until The Revolution" - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/