public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: printing-howto.xml
Date: Fri, 10 Sep 2010 04:35:54 +0000 (UTC)	[thread overview]
Message-ID: <20100910043554.4CFB720051@flycatcher.gentoo.org> (raw)

nightmorph    10/09/10 04:35:54

  Modified:             printing-howto.xml
  Log:
  guidexml fixes; no content change

Revision  Changes    Path
1.80                 xml/htdocs/doc/en/printing-howto.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/printing-howto.xml?rev=1.80&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/printing-howto.xml?rev=1.80&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/printing-howto.xml?r1=1.79&r2=1.80

Index: printing-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -r1.79 -r1.80
--- printing-howto.xml	17 Mar 2010 08:21:02 -0000	1.79
+++ printing-howto.xml	10 Sep 2010 04:35:54 -0000	1.80
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.79 2010/03/17 08:21:02 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.80 2010/09/10 04:35:54 nightmorph Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide>
@@ -589,9 +589,9 @@
 
 <note>
 If you use an HTTPS connection to CUPS, the first time you access the interface
-it <e>may</e> take a very long time before the site comes up. This is because the
-first request triggers the generation of the CUPS SSL certificates which can be a
-very time-consuming job.
+it <e>may</e> take a very long time before the site comes up. This is because
+the first request triggers the generation of the CUPS SSL certificates which can
+be a very time-consuming job.
 </note>
 
 <p>
@@ -1070,5 +1070,4 @@
 </body>
 </section>
 </chapter>
-
 </guide>






             reply	other threads:[~2010-09-10  4:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10  4:35 Joshua Saddler (nightmorph) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-12-25 19:00 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: printing-howto.xml Sven Vermeulen (swift)
2011-03-02  8:59 Joshua Saddler (nightmorph)
2011-02-14  6:33 Jan Kundrat (jkt)
2010-03-17  8:21 Joshua Saddler (nightmorph)
2010-02-23 11:04 Jan Kundrat (jkt)
2010-02-17 18:06 Joshua Saddler (nightmorph)
2010-02-17  7:28 Joshua Saddler (nightmorph)
2009-12-29 19:31 Joshua Saddler (nightmorph)
2009-06-14  9:54 Joshua Saddler (nightmorph)
2009-01-26  7:40 Joshua Saddler (nightmorph)

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=20100910043554.4CFB720051@flycatcher.gentoo.org \
    --to=nightmorph@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