From: "Jan Kundrat" <jkt@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
Date: Mon, 12 Dec 2005 15:41:26 +0000 [thread overview]
Message-ID: <200512121541.jBCFfRRF001614@robin.gentoo.org> (raw)
jkt 05/12/12 15:41:26
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
16:37 < Halcy0n> You are missing a space :)
Revision Changes Path
1.3 +2 -2 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- gcc-upgrading.xml 8 Dec 2005 19:25:55 -0000 1.2
+++ gcc-upgrading.xml 12 Dec 2005 15:41:26 -0000 1.3
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.2 2005/12/08 19:25:55 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.3 2005/12/12 15:41:26 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -166,7 +166,7 @@
<p>
This method requires that you first install <c>gentoolkit</c> if you have not
already done so. Then we will upgrade GCC and switch to the new compiler. We
-will also rebuild the <c>libtool</c> package to ensurethat toolchain is in
+will also rebuild the <c>libtool</c> package to ensure that toolchain is in
healthy state.
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2005-12-12 15:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 15:41 Jan Kundrat [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-10-06 17:41 Josh Saddler
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-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=200512121541.jBCFfRRF001614@robin.gentoo.org \
--to=jkt@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