Robert P. J. Day wrote:
that's entirely a judgment call on the part of the code's maintainer.
if something is both obsolete and broken, then make it depend on
*both* OBSOLETE and BROKEN if you want. no big deal.
Yup.
OBSOLETE = might be broken, no one is planning to maintain it.
BROKEN = known to be broken.
They're by and large orthogonal.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
