From 3e4ee14d58133a798039bfdd6534a6cd7411b046 Mon Sep 17 00:00:00 2001
From: Sylvestre Ledru <sylvestre@debian.org>
Date: Thu, 25 Oct 2018 14:19:06 +0000
Subject: [PATCH] update the clang doc about contributions

llvm-svn: 345267
---
 clang/www/hacking.html | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/clang/www/hacking.html b/clang/www/hacking.html
index f2f98f4..058255b 100755
--- a/clang/www/hacking.html
+++ b/clang/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>
   <!--=====================================================================-->
-- 
2.7.4