> (hmmm... thinking I may have just voleentered :)
It's a dandelion problem -- you pull on it, and you find a whole root
system underneath it.
The problem is: "how do you document an entity where hundreds of unrelated
people check in code everywhere, and your desire for documentation
exceeds the willingness of those hundreds of people to write it."
When Linus decides he wants more documentation, he can make that a
criterion for accepting a patch. He can lay out whatever rules he likes.
My suggestion is: "if your code has an interface to userland, your patch
must have a file in Documentation/ somewhere that documents the interface
to userland."
Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/