<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - It should be easier to find Clang documentation for *current* and *past* releases"
href="https://bugs.llvm.org/show_bug.cgi?id=39614">39614</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>It should be easier to find Clang documentation for *current* and *past* releases
</td>
</tr>
<tr>
<th>Product</th>
<td>Documentation
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>General docs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>guy@alum.mit.edu
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>The GCC web site at gcc.gnu.org does a good job of making available
documentation for the current GCC release and for the most recent minor
releases for all GCC major releases back to GCC 2.95; see
<a href="https://gcc.gnu.org/onlinedocs/">https://gcc.gnu.org/onlinedocs/</a>
The Clang web site at clang.llvm.org has a "User's Manual" link that points to
the Clang *8* documentation, for an under-development-and-not-yet-released
version of Clang.
The manuals for *older* versions are linked to from <a href="http://releases.llvm.org">http://releases.llvm.org</a>.
The Clang home page should 1) explicitly note that the "User's Manual" to which
it links is for a *future* release, not the *current* release and 2) point to
releases.llvm.org for *current* and *past* releases.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>