Re: [patch net-next-2.6] bonding: allow resetting slave failure counters

Wed, Jun 01, 2011 at 09:34:45PM CEST, nicolas.2p.debian@gmail.com wrote:

Le 01/06/2011 21:11, Flavio Leitner a écrit :

quoted

On 06/01/2011 04:03 PM, David Miller wrote:

quoted

From: Jay Vosburgh<redacted>
Date: Wed, 01 Jun 2011 09:13:39 -0700

quoted

The "this dingus was added in version X.Y.Z" is there because
users sometimes read the most recent version of the documentation (that
they get from the internet) and then would become confused when their
older distro driver lacked some option described in the documentation.

I disagree with this whole concept, because distros backport features
like this into their kernel and therefore the feature is showing up in
version X.Y.$(Z-20).

It doesn't matter the version if the user can find the feature, so
distros backporting features works and that info is not useful at all.
However, when the user doesn't find the feature and search the internet,
then that info is helpful.

There are *many* new features that get included into the kernel
without documenting the exact first version that provide them. Why
should we need this for bonding? Also, because we lack a table that
gives the kernel version matching a bonding version, the user is not
really helped by "you need version X.Y.Z of bonding to have this
feature".

I think that doing versioning on multiple parts of the same code is only
confusing. Kernel version should be only version for whole kernel code.
Changes should be only documented in descriptions of changesets. Any
other way is redundant, might be not accurate, and rather confusing.

Jirka

So, I'm not sure it helps...

Nicolas.