On Wed, 21 Mar 2018 21:22:16 +0200 Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx> wrote: > These patches convert files in Documentation/vm to ReST format, add an > initial index and link it to the top level documentation. > > There are no contents changes in the documentation, except few spelling > fixes. The relatively large diffstat stems from the indentation and > paragraph wrapping changes. > > I've tried to keep the formatting as consistent as possible, but I could > miss some places that needed markup and add some markup where it was not > necessary. So I've been pondering on these for a bit. It looks like a reasonable and straightforward RST conversion, no real complaints there. But I do have a couple of concerns... One is that, as we move documentation into RST, I'm really trying to organize it a bit so that it is better tuned to the various audiences we have. For example, ksm.txt is going to be of interest to sysadmin types, who might want to tune it. mmu_notifier.txt is of interest to ... somebody, but probably nobody who is thinking in user space. And so on. So I would really like to see this material split up and put into the appropriate places in the RST hierarchy - admin-guide for administrative stuff, core-api for kernel development topics, etc. That, of course, could be done separately from the RST conversion, but I suspect I know what will (or will not) happen if we agree to defer that for now :) The other is the inevitable merge conflicts that changing that many doc files will create. Sending the patches through Andrew could minimize that, I guess, or at least make it his problem. Alternatively, we could try to do it as an end-of-merge-window sort of thing. I can try to manage that, but an ack or two from the mm crowd would be nice to have. Thanks, jon
