Hi Jon, Em Mon, 12 Sep 2016 10:40:41 -0600 Jonathan Corbet <cor...@lwn.net> escreveu:
> On Mon, 12 Sep 2016 11:47:51 -0300 > Mauro Carvalho Chehab <mche...@s-opensource.com> wrote: > > - Some of this will need wider exposure for a different reason: I suspect > there will be resistance to renaming well-known documents like > SubmittingPatches. Everybody knows it's there and directs people to > it; simply moving it out will create lots of dangling mental links, and > I think people will grumble. I don't really know how to solve that one. Based on the few comments it got on LKML, it seems people are accepting such renames. I already addressed the issues pointed at the review process and I'm ready to submit a final version. Yet, as you're concerned about the renames, I opted to reorder the patch series to do: 1) conversion of the existing development-process to ReST and create the a Sphinx book, prepared to support sub-books; 2) do all changes for the HOWTO/CodingStyle/Submitting*/.. to use the ReST markup, but keeping where they are; 3) rename the files and move them to development-process/ dir; 4) Adjust cross-references; 5) add them at the development-process book. This way, you can apply patches for (1) and (2) on your docs-next branch without stress. This way, if you opt to do steps (3) to (5) after 4.9, we won't lose the efforts done at the ReST conversion. It should also be easy to add an extra patch (or fold it with the rename patch) that would create boiler plate files that would be pointing to the new location, as suggested by Markus. I'll be patchbomb this series in a few. They're already on my development tree. Thanks, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
