Gentoo Archives: gentoo-doc-cvs

From: Jan Kundrat <jkt@×××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
Date: Wed, 13 Sep 2006 14:52:01
Message-Id: 20060913145211.3C64A64780@smtp.gentoo.org
1 jkt 06/09/13 14:52:10
2
3 Modified: gcc-upgrading.xml
4 Log:
5 coding style fixes, *no content change*
6
7 Revision Changes Path
8 1.22 xml/htdocs/doc/en/gcc-upgrading.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.22&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.22&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.21&r2=1.22
13
14 Index: gcc-upgrading.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
17 retrieving revision 1.21
18 retrieving revision 1.22
19 diff -u -r1.21 -r1.22
20 --- gcc-upgrading.xml 13 Sep 2006 14:42:58 -0000 1.21
21 +++ gcc-upgrading.xml 13 Sep 2006 14:52:10 -0000 1.22
22 @@ -1,5 +1,5 @@
23 <?xml version='1.0' encoding="UTF-8"?>
24 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.21 2006/09/13 14:42:58 jkt Exp $ -->
25 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.22 2006/09/13 14:52:10 jkt Exp $ -->
26
27 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
28
29 @@ -187,9 +187,13 @@
30 method</uri> is faster and requires use of the <c>revdep-rebuild</c> tool from
31 package <c>gentoolkit</c> while the <uri
32 link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the entire
33 -system from scratch so it will make use of new GCC features. It's up to you to decide which of these two ways you will choose. In most cases, the first
34 -method is sufficient.</p>
35 -<p>If you upgrade from gcc 3.3 to 4.1, do not use the method based on
36 +system from scratch so it will make use of new GCC features. It's up to you to
37 +decide which of these two ways you will choose. In most cases, the first
38 +method is sufficient.
39 +</p>
40 +
41 +<p>
42 +If you upgrade from gcc 3.3 to 4.1, do not use the method based on
43 revdep-rebuild, but do a <uri link="#upgrade-3.3-to-3.4-emerge-e">complete
44 system rebuild</uri>.
45 </p>
46
47
48
49 --
50 gentoo-doc-cvs@g.o mailing list