swift 08/05/19 21:02:24 Modified: gcc-upgrading.xml Log: Coding style
Revision Changes Path 1.27 xml/htdocs/doc/en/gcc-upgrading.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.27&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.27&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.26&r2=1.27 Index: gcc-upgrading.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- gcc-upgrading.xml 2 Apr 2007 23:13:45 -0000 1.26 +++ gcc-upgrading.xml 19 May 2008 21:02:24 -0000 1.27 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.26 2007/04/02 23:13:45 jkt Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.27 2008/05/19 21:02:24 swift Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> @@ -56,8 +56,8 @@ <p> This guide will document the necessary steps required to perform a seamless upgrade of the compiler used by your Gentoo box. A specific section is -dedicated to the <uri link="#upgrade-3.3-to-3.4">upgrade from GCC 3.3 to 3.4</uri> -and issues with <c>libstdc++</c>. A second specific +dedicated to the <uri link="#upgrade-3.3-to-3.4">upgrade from GCC 3.3 to +3.4</uri> and issues with <c>libstdc++</c>. A second specific section is for users <uri link="#first-install">first installing</uri> Gentoo using a stage3 tarball, after a new GCC major/minor version has been released. </p> @@ -124,7 +124,7 @@ <p> To be completely safe that your system is in a sane state, you <e>must</e> -rebuild the toolchain and then world to make use of the new compiler. +rebuild the toolchain and then world to make use of the new compiler. </p> <pre caption="Rebuilding system"> -- [email protected] mailing list
