David S. Miller Awoke this dragon, who will now respond:
> From: Ian Molton <spyro@armlinux.org>
> Date: Sun, 21 Apr 2002 05:31:43 +0100
> Sure, except no-one cares about this point.
> the documentation is the 'sticky wicket'...
>
> Incorrect. The argument for the documentation was that it along with
> other things wrt. BK create some "barrier to entry" for Linux kernel
> development and almost force someone to use BK. That someone just
> submitting patches is somehow "left out".
>
> Al is showing that these claims are not well founded at all.
hmm.
I take it as blatently obvious that BK isnt a barrier to entry, as the old
methods still work fine.
what I /do/ appreciate is that by including directions to proprietary tools
in the docs, we are heading down a greased incline, so to speak.
Extreme example:
Include docs on 'how to avoid a pesky kernel compile' that teach how to
install windows, not linux because its an 'all in one' install with 'no
hassle'...
see how many people compile their own kernels afer that...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Apr 23 2002 - 22:00:28 EST