Documentation cleanup review process?

Dear llvm-dev,

As I’ve been working with llvm sources on a prototype backend, it seems to me that much of the documentation on llvm internals is, shall we say, wanting. (I’m looking at you particularly, tablegen.)

I can clean up documentation issues and clarify in the .rst files as I’m learning, but the code submission process is silent on how documentation changes make it into master. At this point, even CODE_OWNERS.TXT is silent on who is responsible for the doc directory.

Pointers would be helpful. Thank you very much.

I don’t think documentation works much different than source-code. I.e., patches welcome, and you can always upload a diff for e.g. any of the .rst files in the doc directory. Usually good candidates for reviewers are people who last touched the same piece of code/text, which you can find out with a git/svn blame.


I’ve been following the standard review and commit process for documentation updates for a number of issues recently (see for example Ultimately, take a look at who has recently updated the relevant area of the doc and/or the tool/feature itself.