[cmake-developers] User vs CMake include mismatch handling

[Brad King]

On 11/17/2010 04:50 PM, Alexander Neundorf wrote:
> That's why this policy has to be set to NEW to avoid breakage.

As Dave said, the entire design of policies is based on defaulting to WARN,
as in "do what I did before but tell people it is no longer the right way".
If that doesn't make sense in this use case then the answer is not a policy.

-Brad