diff options
author | Sylvestre Ledru <sylvestre@debian.org> | 2018-10-25 14:19:06 +0000 |
---|---|---|
committer | Sylvestre Ledru <sylvestre@debian.org> | 2018-10-25 14:19:06 +0000 |
commit | e9e6d674bbb124ff6fdca9731505070e0860b782 (patch) | |
tree | 444bda9b9044116e34bdec786a512c7a2d87ae43 /www | |
parent | b716dcf4d9808f273f8752751ecd53901bc627fc (diff) |
update the clang doc about contributions
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345267 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'www')
-rwxr-xr-x | www/hacking.html | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/www/hacking.html b/www/hacking.html index f2f98f4a9f..058255b787 100755 --- a/www/hacking.html +++ b/www/hacking.html @@ -276,9 +276,8 @@ Testing Time: 81.52s <!--=====================================================================--> <p>To return changes to the Clang team, unless you have checkin - privileges, the preferred way is to send patch files to the - cfe-commits mailing list, with an explanation of what the patch is - for. clang follows <a + privileges, the preferred way is to send patch files + <a href="https://llvm.org/docs/Contributing.html#how-to-submit-a-patch">using LLVM's Phabricator</a> with an explanation of what the patch is for. Clang follows <a href="http://llvm.org/docs/DeveloperPolicy.html">LLVM's developer policy</a>. If your patch requires a wider discussion (for example, because it is an architectural change), you can use the cfe-dev mailing list.</p> @@ -299,6 +298,8 @@ Testing Time: 81.52s <p>Note that the paths embedded in the patch depend on where you run it, so changing directory to the llvm/tools/clang directory is recommended.</p> + <p>It is also possible to <a href="https://llvm.org/docs/GettingStarted.html#sending-patches-with-git">use git to contribute</a> to Clang.</p> + <!--=====================================================================--> <h2 id="irgen">LLVM IR Generation</h2> <!--=====================================================================--> |