From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
	by nuthatch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-doc-cvs+bounces-2062-garchives=archives.gentoo.org@gentoo.org>)
	id 1GNW5p-0000AU-Bf
	for garchives@archives.gentoo.org; Wed, 13 Sep 2006 14:52:01 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
	by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k8DEqCnL007315;
	Wed, 13 Sep 2006 14:52:12 GMT
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k8DEqBsw029406
	for <gentoo-doc-cvs@lists.gentoo.org>; Wed, 13 Sep 2006 14:52:11 GMT
Received: from lark (lark.gentoo.osuosl.org [140.211.166.177])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.gentoo.org (Postfix) with SMTP id 3C64A64780
	for <gentoo-doc-cvs@lists.gentoo.org>; Wed, 13 Sep 2006 14:52:11 +0000 (UTC)
Received: by lark (sSMTP sendmail emulation); Wed, 13 Sep 2006 14:52:10 +0000
From: "Jan Kundrat" <jkt@lark.gentoo.org>
Date: Wed, 13 Sep 2006 14:52:10 +0000
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
Message-Id: <20060913145211.3C64A64780@smtp.gentoo.org>
Precedence: bulk
List-Post: <mailto:gentoo-doc-cvs@lists.gentoo.org>
List-Help: <mailto:gentoo-doc-cvs+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-doc-cvs+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-doc-cvs+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-doc-cvs.gentoo.org>
X-BeenThere: gentoo-doc-cvs@gentoo.org
Reply-to: docs-team@lists.gentoo.org
X-Archives-Salt: d89def8c-62a8-4fcf-b9b0-3bfff63a3436
X-Archives-Hash: 74f78dae283798ff0ef3f823bb334c55

jkt         06/09/13 14:52:10

  Modified:             gcc-upgrading.xml
  Log:
  coding style fixes, *no content change*

Revision  Changes    Path
1.22                 xml/htdocs/doc/en/gcc-upgrading.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.22&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.22&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.21&r2=1.22

Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- gcc-upgrading.xml	13 Sep 2006 14:42:58 -0000	1.21
+++ gcc-upgrading.xml	13 Sep 2006 14:52:10 -0000	1.22
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.21 2006/09/13 14:42:58 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.22 2006/09/13 14:52:10 jkt Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -187,9 +187,13 @@
 method</uri> is faster and requires use of the <c>revdep-rebuild</c> tool from
 package <c>gentoolkit</c> while the <uri
 link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the entire
-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
-method is sufficient.</p>
-<p>If you upgrade from gcc 3.3 to 4.1, do not use the method based on
+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
+method is sufficient.
+</p>
+
+<p>
+If you upgrade from gcc 3.3 to 4.1, do not use the method based on
 revdep-rebuild, but do a <uri link="#upgrade-3.3-to-3.4-emerge-e">complete
 system rebuild</uri>.
 </p>



-- 
gentoo-doc-cvs@gentoo.org mailing list