On Wed, 15 Feb 2017 13:28:54 +0100 Remy Leone <remy.leone@xxxxxxxxx> wrote: > I got a question: what are the next steps for a patch before being > merged? From what I understood, there is lieutenants that maintain a > series of patches before Linus review and merge them. On top of which > repository should I continue working for example for fixing the broken > links? Linus Torvalds one? I haven't had a chance to play with this one; I'll do so and presumably merge it before the weekend so it can get into 4.11. (One small request: when you submit an updated patch, it's good to say what changed, usually below the "---" at the bottom of the changelog). When you get around to fixing other docs, it really depends; the maintainership of files under Documentation/ is sometimes a bit fuzzy. It never hurts to send patches to me. The get_maintainer.pl script can tell you who else might be interested. The docs-next repo contains the closest approximation of the next state of the documentation directory. But working against any reasonably current repo should be find unless you stumble into a document that's actively being converted to Sphinx. Thanks, jon -- 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
