This would only be helpful if you also had a description of what the
user is expected to change. (And once you have this, you might as
well automate the process a little more, as I've just described in
Just telling the user that there might be problems isn't very helpful,
in particular since most such version conflicts would be false alarms,
e.g. name changes of some obscure controller I don't have anyway. I
think most people are aware of the fact that "make oldconfig" may
produce nonsense, but it's still annoying if it does.
Another easy extension to consider: after "make oldconfig", print
the options that were found in .config, but which don't exist anymore.
I've actually proposed this already two years ago, see also
-- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina email@example.com / /_http://www.almesberger.net/____________________________________________/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/