Author: sylvestre
Date: Thu Oct 25 07:19:06 2018
New Revision: 345267
URL: http://llvm.org/viewvc/llvm-project?rev=345267&view=rev
Log:
update the clang doc about contributions
Modified:
cfe/trunk/www/hacking.html
Modified: cfe/trunk/www/hacking.html
URL:
http://llvm.org/viewvc/llvm-project/cfe/trunk/www/hacking.html?rev=345267&r1=345266&r2=345267&view=diff
==============================================================================
--- cfe/trunk/www/hacking.html (original)
+++ cfe/trunk/www/hacking.html Thu Oct 25 07:19:06 2018
@@ -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>
<!--=====================================================================-->
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
