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: power-management-guide.xml
Date: Mon, 28 Mar 2011 10:26:10 +0000 (UTC)	[thread overview]
Message-ID: <20110328102610.DFF8220054@flycatcher.gentoo.org> (raw)

nightmorph    11/03/28 10:26:10

  Modified:             power-management-guide.xml
  Log:
  typo fix, no content change. bug 360277.

Revision  Changes    Path
1.46                 xml/htdocs/doc/en/power-management-guide.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.46&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.46&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.45&r2=1.46

Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- power-management-guide.xml	2 Mar 2011 09:18:04 -0000	1.45
+++ power-management-guide.xml	28 Mar 2011 10:26:10 -0000	1.46
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.45 2011/03/02 09:18:04 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.46 2011/03/28 10:26:10 nightmorph Exp $ -->
 
 <guide>
 <title>Power Management Guide</title>
@@ -65,7 +65,7 @@
 sections will work. This includes BIOS settings, kernel configuration and some
 simplifications in user land. The following three chapters focus on devices
 that typically consume most energy - processor, display and hard drive. Each
-can be configured seperately. <uri link="#doc_chap3">CPU Power Management</uri>
+can be configured separately. <uri link="#doc_chap3">CPU Power Management</uri>
 shows how to adjust the processor's frequency to save a maximum of energy
 without losing too much performance. A few different tricks prevent your hard
 drive from working unnecessarily often in <uri link="#doc_chap5">Disk Power






             reply	other threads:[~2011-03-28 10:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 10:26 Joshua Saddler (nightmorph) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-07 13:25 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: power-management-guide.xml Sven Vermeulen (swift)
2013-01-14  6:19 Joshua Saddler (nightmorph)
2011-09-30 15:07 Camille Huot (cam)
2011-09-23 18:41 Sven Vermeulen (swift)
2011-08-17  7:19 Sven Vermeulen (swift)
2011-08-17  7:10 Sven Vermeulen (swift)
2011-03-02  9:18 Joshua Saddler (nightmorph)
2010-07-18  6:36 Jan Kundrat (jkt)
2010-04-05  1:25 Joshua Saddler (nightmorph)
2010-01-22 15:48 Joshua Saddler (nightmorph)
2009-08-12  2:24 Joshua Saddler (nightmorph)
2009-08-05 14:51 Joshua Saddler (nightmorph)
2009-05-14 15:01 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=20110328102610.DFF8220054@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