From 71dcbe1e88b446ae7f405da1b3006b966ccc6ca6 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Wed, 30 Sep 2020 22:36:44 -0700 Subject: [PATCH] We don't need two different ways to get commit access, just simplify the policy here so that old SVN users and new contributors do the same thing. --- llvm/docs/DeveloperPolicy.rst | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/llvm/docs/DeveloperPolicy.rst b/llvm/docs/DeveloperPolicy.rst index 0af0f1d..7db365e 100644 --- a/llvm/docs/DeveloperPolicy.rst +++ b/llvm/docs/DeveloperPolicy.rst @@ -298,11 +298,10 @@ 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 `_ with your GitHub username. +`Chris `_ with your GitHub username. This is true +for former contributors with SVN access as well as new contributors. Prior to obtaining commit access, it is common practice to request that someone with commit access commits on your behalf. When doing so, please @@ -345,12 +344,6 @@ 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 - Transferring from SVN -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -If you had commit access to SVN and would like to request commit access to -GitHub, please email `llvm-admin `_ with your -SVN username and GitHub username. - .. _discuss the change/gather consensus: Making a Major Change -- 2.7.4