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: ltsp.xml
Date: Sat, 23 Dec 2006 03:55:47 +0000	[thread overview]
Message-ID: <20061223035548.2510364823@smtp.gentoo.org> (raw)

nightmorph    06/12/23 03:55:47

  Modified:             ltsp.xml
  Log:
  fixed links to documentation in troubleshooting section et al, bug 158589

Revision  Changes    Path
1.19                 xml/htdocs/doc/en/ltsp.xml

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

Index: ltsp.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/ltsp.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- ltsp.xml	29 Nov 2006 15:48:57 -0000	1.18
+++ ltsp.xml	23 Dec 2006 03:55:47 -0000	1.19
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ltsp.xml,v 1.18 2006/11/29 15:48:57 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ltsp.xml,v 1.19 2006/12/23 03:55:47 nightmorph Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/ltsp.xml">
@@ -20,8 +20,8 @@
 
 <license/>
 
-<version>1.11</version>
-<date>2006-04-04</date>
+<version>1.12</version>
+<date>2006-12-22</date>
 
 <chapter>
 <title>Introduction</title>
@@ -332,8 +332,8 @@
 <body>
 
 <p>
-There are many options to configure your workstations, visit 
-<uri>http://www.ltsp.org/documentation/ltsp-3.0-4-en.html#AEN903</uri> 
+There are many options to configure your workstations, visit
+<uri>http://ltsp.mirrors.tds.net/pub/ltsp/docs/ltsp-4.1-en.html#AEN1190</uri>
 for a full description of <path>/opt/ltsp/i386/etc/lts.conf</path>.
 </p>
 
@@ -442,13 +442,17 @@
 </p>
 
 <ul>
-<li>The official documentation: 
-<uri>http://www.ltsp.org/documentation/</uri>, especially the 
-Troubleshooting section.</li>
+  <li>
+    The official documentation:
+    <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/Documentation</uri>,
+    especially the Troubleshooting section.
+  </li>
 <li>The gentoo IRC channel: irc.freenode.org #gentoo</li>
 <li>The ltsp irc channel: irc.freenode.org #ltsp</li>
-<li>The ltsp mailinglists <uri>http://ltsp.org/mailinglists.php</uri> 
-are full of some real good knowledge.</li>
+  <li>
+    The ltsp mailinglists <uri>http://ltsp.org/mailinglists.php</uri> are full
+    of some real good knowledge.
+  </li>
 </ul>
 </body>
 </section>



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



             reply	other threads:[~2006-12-23  3:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-23  3:55 Josh Saddler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-19 21:16 [gentoo-doc-cvs] cvs commit: ltsp.xml Sven Vermeulen
2007-05-03  5:56 Josh Saddler
2006-04-04 15:25 Xavier Neys
2006-02-22 14:41 Shyam Mani
2005-07-28 12:34 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=20061223035548.2510364823@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