public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Josh Saddler" <nightmorph@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
Date: Fri,  6 Oct 2006 17:41:37 +0000	[thread overview]
Message-ID: <20061006174138.3FAB364244@smtp.gentoo.org> (raw)

nightmorph    06/10/06 17:41:37

  Modified:             gcc-upgrading.xml
  Log:
  updated gcc-upgrading guide for bug 148126

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

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

Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- gcc-upgrading.xml	13 Sep 2006 23:39:00 -0000	1.24
+++ gcc-upgrading.xml	6 Oct 2006 17:41:37 -0000	1.25
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.24 2006/09/13 23:39:00 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.25 2006/10/06 17:41:37 nightmorph Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -25,8 +25,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>20</version>
-<date>2006-09-13</date>
+<version>21</version>
+<date>2006-10-06</date>
 
 <chapter id="intro">
 <title>Introduction</title>
@@ -112,7 +112,7 @@
 <comment>(Please substitute "i686-pc-linux-gnu-4.1.1" with the GCC
 version and CHOST settings you've upgraded to:)</comment>
 # <i>gcc-config i686-pc-linux-gnu-4.1.1</i>
-# <i>source /etc/profile</i>
+# <i>env-update &amp;&amp; source /etc/profile</i>
 
 <comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this
 example) you will have to run fix_libtool_files.sh manually</comment>



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



             reply	other threads:[~2006-10-06 17:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 17:41 Josh Saddler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-03  3:35 [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml Joshua Saddler
2008-05-19 21:02 Sven Vermeulen
2007-04-02 23:13 Jan Kundrat
2006-09-13 23:39 Jan Kundrat
2006-09-13 23:20 Jan Kundrat
2006-09-13 14:52 Jan Kundrat
2006-09-13 14:42 Jan Kundrat
2006-09-07 11:06 Lukasz Damentko
2006-09-06  2:14 vapier
2006-09-04 20:48 Josh Saddler
2006-09-02  5:18 Lukasz Damentko
2006-09-02  4:16 vapier
2006-08-31  0:08 Josh Saddler
2006-05-26 20:45 Josh Saddler
2006-03-01 20:17 Jan Kundrat
2006-03-01  1:54 Marcelo Goes
2006-02-25  9:37 Jan Kundrat
2006-02-09 17:40 Jan Kundrat
2006-02-09 16:15 Jan Kundrat
2006-02-09 16:06 Jan Kundrat
2006-02-02 15:59 Xavier Neys
2006-01-30 15:32 Jan Kundrat
2005-12-14 20:03 Jan Kundrat
2005-12-12 15:41 Jan Kundrat
2005-12-08 19:25 Jan Kundrat
2005-12-08 19:21 Jan Kundrat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061006174138.3FAB364244@smtp.gentoo.org \
    --to=nightmorph@lark.gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox