This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[wwwdocs] egcs-1.1/egcs-1.1-branch.html -- use <code> instead of <tt>
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Sun, 2 Sep 2018 15:22:13 +0200 (CEST)
- Subject: [wwwdocs] egcs-1.1/egcs-1.1-branch.html -- use <code> instead of <tt>
It appears we copied from ourselves, so what I fixed for GCC 2.95
already was, pretty much identically, there for egcs 1.1.
Fixued thusly, making also this page HTML 5.
Gerald
Index: egcs-1.1/egcs-1.1-branch.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/egcs-1.1/egcs-1.1-branch.html,v
retrieving revision 1.9
diff -u -r1.9 egcs-1.1-branch.html
--- egcs-1.1/egcs-1.1-branch.html 1 Sep 2018 23:42:02 -0000 1.9
+++ egcs-1.1/egcs-1.1-branch.html 2 Sep 2018 12:27:45 -0000
@@ -15,11 +15,11 @@
EGCS sources.</li>
<li> Track just the EGCS 1.1 release. You can convert your existing CVS tree
to track the EGCS 1.1 release with the command:
- <br /><tt>cvs update -regcs_1_1_branch</tt></li>
+ <br /><code>cvs update -regcs_1_1_branch</code></li>
<li> Track both the EGCS 1.1 release and the development sources. You will
need to check out the EGCS 1.1 release in a separate directory using the
command:
- <br /><tt>cvs co -regcs_1_1_branch egcs</tt></li>
+ <br /><code>cvs co -regcs_1_1_branch egcs</code></li>
</ol>
<p>Considering that the primary focus of the project is on the egc-1.1 release,