Re: [RFC PATCH] feature-removal: add documentation for exportedsymbols going away

[Andrew Morton]

On Thu, 14 Feb 2008 01:22:48 +0200
Adrian Bunk <bunk@xxxxxxxxxx> wrote:

> I don't get your point why bigger API changes should still be allowed 
> without any advance warning while removing an export should require 
> deprecation periods.

Because the cost to us of giving people a few months warning is miniscule,
and doing so a) is courteous to our users and b) possibly avoids driving
away testers.

otoh the cost to us of avoiding large API changes is much much higher, so
the tradeoff has a different outcome.

> If you want to offer a stable API for external modules then please do 
> it completely and with all consequences.

Sorry, but you have this belief that if we do X in one case then we should
rigorously do X in all cases.  That everything we do sets precedents which
must be forever and in all cases followed.  That it is all about rules and
sticking to them.  That if you can catch person A taking action B then you
can trap that person into doing B in all cases for ever more.

Well it doesn't work like that.  Each case is different and each case has
pros and cons and each one needs to be weighed according to those pros and
cons.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/