diff options
| author | Jim Lin <tclin914@gmail.com> | 2020-01-08 10:43:45 +0800 |
|---|---|---|
| committer | Jim Lin <tclin914@gmail.com> | 2020-01-08 10:44:44 +0800 |
| commit | f7ca0c761979f0a06894571245a913cd8e2dbfce (patch) | |
| tree | f30c3033e2a92be806a2fa2d92325036d95321bd /llvm/docs | |
| parent | 7e7f849a6d94f77f1a29630419acb7226051f4b6 (diff) | |
| download | bcm5719-llvm-f7ca0c761979f0a06894571245a913cd8e2dbfce.tar.gz bcm5719-llvm-f7ca0c761979f0a06894571245a913cd8e2dbfce.zip | |
[docs] Fix duplicate explicit target name: developer policy
Diffstat (limited to 'llvm/docs')
| -rw-r--r-- | llvm/docs/GettingStarted.rst | 4 |
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 |
