Alan Cox wrote:
[snip]
A cleaned-up, consistent, and out-of-tree friendly way of handling API
changes might help us all.
The problem is that its very impractical. If I change a kernel API I fix
up the in tree users and test those I can, that's "accepted practice" -
you make mess doing a job you clean it up. I can't do that for out of
tree code because its out of tree.
Thanks for the thoughtful reply. _And_ for taking the time to look at
the code.
I guess my half-assed notion is to have a single file w/"#ifdef-able"
entries that flag API changes. It at least would give me/us a single
point of reference, and avoid the rather ugly version checking. "LDDx"
is fine, and lwn.net has saved my ass more times than I can count, but a
single peg on which to hang my out-of-tree hat would seem useful.
Thanks again,
Bill
--
--------------------------------------------
William D Waddington
Bainbridge Island, WA, USA
[email protected]
--------------------------------------------
"Even bugs...are unexpected signposts on
the long road of creativity..." - Ken Burtch
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
