Tweak the guidelines for when one should send patches to cfe-commits vs. cfe-dev

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@145000 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/www/hacking.html b/www/hacking.html
index bedb2b6a588e2d300873a94d9b1593494eabe684..eef9d82816adc556da3ba9161b3cc2f8d932485b 100644 (file)
--- a/www/hacking.html
+++ b/www/hacking.html
@@ -255,11 +255,10 @@ 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.
-  Or, if you have questions, or want to have a wider discussion of what
-  you are doing, such as if you are new to Clang development, you can use
-  the cfe-dev mailing list also.
-  </p>
+  cfe-commits mailing list, with an explanation of what the patch is
+  for.  If your patch requires a wider discussion (for example,
+  because it is an architectural change), you can use the cfe-dev
+  mailing list.  </p>
 
   <p>To create these patch files, change directory
   to the llvm/tools/clang root and run:</p>