On Fri, Apr 6, 2012 at 1:28 PM, Jonathan Corbet <corbet@xxxxxxx> wrote: > On Fri, 6 Apr 2012 13:01:17 -0700 > Andrew Lutomirski <luto@xxxxxxx> wrote: > >> This has been bugging me for awhile. Is there any interest in moving >> the manpages into the kernel source tree? Then there could be a >> general requirement that new APIs get documented when they're written. > > Man page (or other documentation) requirements for patch acceptance are a > regular kernel summit feature. People seem to think it's a good idea, but > actual enforcement of such requirements always seems to be lacking. Lots > of people have kind of given up trying. I don't really see that adding > the man pages to the tree would help, but I could be wrong... > If it's in the source, then I can send it with git format-patch. If it's out of tree, I have to find the tree, clone the tree, figure out how to submit, and send separate emails. And then whoever checks that I documented it has to figure out where I sent it and how to read it and then try to decide which documentation submission matches which patch submission. (Also, if it's in-tree, then I can build the docs from a kernel tree and have the latest ones. That could be nice.) --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
