RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-26 04:40:38 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: Update instructions for requesting commit access

Browse Source
This commit is contained in:
Tom Stellard 2019-10-24 15:46:08 -07:00
parent b567b75641
commit 2e60739b40
1 changed files with 11 additions and 42 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

53
docs/DeveloperPolicy.rst
View File

@ -334,31 +334,14 @@ omissions can be handled by sending a reply to the commits mailing list.
Obtaining Commit Access
-----------------------
New Contributors
^^^^^^^^^^^^^^^^
We grant commit access to contributors with a track record of submitting high
quality patches. If you would like commit access, please send an email to
`Chris <mailto:clattner@llvm.org>`_ with the following information:
`Chris <mailto:clattner@llvm.org>`_ with your GitHub username.
#. The user name you want to commit with, e.g. "hacker".
#. The full name and email address you want message to llvm-commits to come
from, e.g. "J. Random Hacker <hacker@yoyodyne.com>".
#. A "password hash" of the password you want to use, e.g. "``2ACR96qjUqsyM``".
Note that you don't ever tell us what your password is; you just give it to
us in an encrypted form. To get this, run "``htpasswd``" (a utility that
comes with apache) in *crypt* mode (often enabled with "``-d``"), or find a web
page that will do it for you. Note that our system does not work with MD5
hashes. These are significantly longer than a crypt hash - e.g.
"``$apr1$vea6bBV2$Z8IFx.AfeD8LhqlZFqJer0``", we only accept the shorter crypt hash.
Once you've been granted commit access, you should be able to check out an LLVM
tree with an SVN URL of "https://username@llvm.org/..." instead of the normal
anonymous URL of "http://llvm.org/...". The first time you commit you'll have
to type in your password. Note that you may get a warning from SVN about an
untrusted key; you can ignore this. To verify that your commit access works,
please do a test commit (e.g. change a comment or add a blank line). Your first
commit to a repository may require the autogenerated email to be approved by a
moderator of the mailing list.
Your first commit to a repository may require the autogenerated email to be
approved by a moderator of the mailing list.
This is normal and will be done when the mailing list owner has time.
If you have recently been granted commit access, these policies apply:
@ -394,28 +377,14 @@ after they are committed, depending on the nature of the change). You are
encouraged to review other peoples' patches as well, but you aren't required
to do so.
Current Contributors - Transfering from SVN
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If you had commit access to SVN and would like to request commit access to
GitHub, please email `llvm-admin <mailto:llvm-admin@lists.llvm.org>`_ with your
SVN username and GitHub username.
.. _discuss the change/gather consensus:
Obtaining Commit Access to the GitHub Repository
------------------------------------------------
We are currently in the process of migrating the project's source code from SVN
to a git repository on GitHub. We are maintaining a file in SVN to map
SVN usernames to GitHub usernames, so we can automatically grant access to
existing committers when we complete the migration to GitHub. In order to
request commit access, check out the github-usernames.txt file in meta/trunk and
add a line in the form of $SVN_USERNAME:$GITHUB_USERNAME and commit it. For
example:
.. code:: console
mkdir tmp-llvm-svn
cd tmp-llvm-svn
svn co https://$SVN_USERNAME@llvm.org/svn/llvm-project/meta/trunk
echo "$SVN_USERNAME:$GITHUB_USERNAME" >> trunk/github-usernames.txt
cd trunk
svn commit -m "Request commit access for $SVN_USERNAME"
Making a Major Change
---------------------