summaryrefslogtreecommitdiffstats
path: root/llvm/docs
diff options
context:
space:
mode:
Diffstat (limited to 'llvm/docs')
-rw-r--r--llvm/docs/GettingStarted.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/llvm/docs/GettingStarted.rst b/llvm/docs/GettingStarted.rst
index 6dfca656d43..35c021ee320 100644
--- a/llvm/docs/GettingStarted.rst
+++ b/llvm/docs/GettingStarted.rst
@@ -494,8 +494,8 @@ Once a patch is reviewed, you should rebase it, re-test locally, and commit the
changes to LLVM's master branch. This is done using `git push` if you have the
required access rights. See `committing a change
<Phabricator.html#committing-a-change>`_ for Phabricator based commits or
-`Developer Policy <DeveloperPolicy.html#obtaining-commit-access>`_ for commit
-access.
+`obtaining commit access <DeveloperPolicy.html#obtaining-commit-access>`_
+for commit access.
LLVM currently has a linear-history policy, which means that merge commits are
not allowed. The `llvm-project` repo on github is configured to reject pushes
OpenPOWER on IntegriCloud