summaryrefslogtreecommitdiff
path: root/docs/GettingStarted.rst
Commit message (Collapse)AuthorAge
* GettingStarted.rst: s/&/&/gNAKAMURA Takumi2012-10-11
| | | | git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@165690 91177308-0d34-0410-b5e6-96231b3b80d8
* GettingStarted.rst: Fix the label to DeveloperPolicy.html.NAKAMURA Takumi2012-10-11
| | | | git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@165689 91177308-0d34-0410-b5e6-96231b3b80d8
* docs: Attempt to fix PR14053.Sean Silva2012-10-10
| | | | | | | | | | | | | | | Hypothesis 1: use of `.. code::` directive instead of `.. code-block::` is causing Sphinx to discard the block. On my machine, `.. code::` renders fine. However, I don't think that `.. code::` is actually a legit Sphinx directive. I believe that on my machine Sphinx is falling back to just displaying it monospace with no syntax, whereas llvm.org's Sphinx is just discarding it. This is truly "remote debugging" since I can't reproduce this on my machine. It would be helpful to be able to see the llvm.org Sphinx build logs; if that's possible please let me know. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@165632 91177308-0d34-0410-b5e6-96231b3b80d8
* Silence Sphinx warnings.Sean Silva2012-10-07
| | | | | | | Found the fix on this page: http://permalink.gmane.org/gmane.comp.python.sphinx.devel/112 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@165380 91177308-0d34-0410-b5e6-96231b3b80d8
* Sphinxify the GettinStarted documentation.Bill Wendling2012-10-07
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@165372 91177308-0d34-0410-b5e6-96231b3b80d8