Tweak documentation.

1. Having "get started", "get involved", and "hacking" makes it hard to find
   how to send patches, so add a link from "get involved" to "hacking".
2. Remove an almost 5 year old note on the test running meachanism changing
   soon.
3. Let "hacking" link to the LLVM developer policy.

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

diff --git a/www/get_involved.html b/www/get_involved.html
index 5d16db952b6f98676c76c5488ff73ecceca4de6c..06fee594200a718cc5e90b58956cd2a7f5a3ea3b 100644 (file)
--- a/www/get_involved.html
+++ b/www/get_involved.html
@@ -21,6 +21,11 @@ and contribute to its development.  Alternatively, maybe you just want to follow
 the development of the project to see it progress.
 </p>
 
+<h2>Contribute</h2>
+
+See the <a href="hacking.html">hacking</a> document for information on how
+to author patches.
+
 <h2>Follow what's going on</h2>
 
 <p>Clang is a subproject of the <a href="http://llvm.org">LLVM Project</a>, but

diff --git a/www/hacking.html b/www/hacking.html
index d7a8701f1dc4eb2fdade2a30d36a3fb870dcd428..4535ef4a137ebcd22d6fa6101125b4dc50ce098d 100644 (file)
--- a/www/hacking.html
+++ b/www/hacking.html
@@ -111,9 +111,6 @@
   <h2 id="testing">Testing</h2>
   <!--=====================================================================-->
 
-  <p><i>[Note: The test running mechanism is currently under revision, so the
-  following might change shortly.]</i></p>
-
   <!--=====================================================================-->
   <h3 id="testingNonWindows">Testing on Unix-like Systems</h3>
   <!--=====================================================================-->
@@ -279,9 +276,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.  If your patch requires a wider discussion (for example,
-  because it is an architectural change), you can use the cfe-dev
-  mailing list.  </p>
+  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>
 
   <p>To create these patch files, change directory
   to the llvm/tools/clang root and run:</p>