[PATCH] D72077: [docs] Improve HowTo commit changes from git
Alexander Lanin via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Thu Jan 2 14:59:09 PST 2020
AlexanderLanin updated this revision to Diff 235958.
AlexanderLanin added a comment.
Hups, thanks.
I do not have commit rights to the repository, someone please commit this change.
Alexander Lanin <alex at lanin.de>
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D72077/new/
https://reviews.llvm.org/D72077
Files:
llvm/docs/GettingStarted.rst
Index: llvm/docs/GettingStarted.rst
===================================================================
--- llvm/docs/GettingStarted.rst
+++ llvm/docs/GettingStarted.rst
@@ -491,7 +491,11 @@
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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`.
+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.
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D72077.235958.patch
Type: text/x-patch
Size: 836 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20200102/5ccd43c5/attachment.bin>
More information about the llvm-commits
mailing list