summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNico Weber <nicolasweber@gmx.de>2014-06-12 21:15:10 +0000
committerNico Weber <nicolasweber@gmx.de>2014-06-12 21:15:10 +0000
commit39f17b6d46ec4e0137df07ad98aebde4f9b5208d (patch)
treedea49e189938dc505b5a8248cff0b1be5b47089c
parenta3089bd7e5bb66993610cd51ee1fb4a8b7c47f42 (diff)
downloadbcm5719-llvm-39f17b6d46ec4e0137df07ad98aebde4f9b5208d.tar.gz
bcm5719-llvm-39f17b6d46ec4e0137df07ad98aebde4f9b5208d.zip
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. llvm-svn: 210826
-rw-r--r--clang/www/get_involved.html5
-rw-r--r--clang/www/hacking.html10
2 files changed, 9 insertions, 6 deletions
diff --git a/clang/www/get_involved.html b/clang/www/get_involved.html
index 5d16db952b6..06fee594200 100644
--- a/clang/www/get_involved.html
+++ b/clang/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/clang/www/hacking.html b/clang/www/hacking.html
index d7a8701f1dc..4535ef4a137 100644
--- a/clang/www/hacking.html
+++ b/clang/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>
OpenPOWER on IntegriCloud