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: alsa-guide.xml
Date: Wed, 31 Jan 2007 16:39:26 +0000	[thread overview]
Message-ID: <E1HCIUY-0006DD-OF@lark.gentoo.org> (raw)

nightmorph    07/01/31 16:39:26

  Modified:             alsa-guide.xml
  Log:
  typo fix, should have been module-rebuild not module rebuild

Revision  Changes    Path
1.72                 xml/htdocs/doc/en/alsa-guide.xml

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

Index: alsa-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -r1.71 -r1.72
--- alsa-guide.xml	31 Jan 2007 15:54:35 -0000	1.71
+++ alsa-guide.xml	31 Jan 2007 16:39:26 -0000	1.72
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.71 2007/01/31 15:54:35 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.72 2007/01/31 16:39:26 nightmorph Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -423,8 +423,8 @@
 Please note that you will have to run <c>emerge alsa-driver</c> after every
 kernel (re)compile, as the earlier drivers are deleted. To make this task
 easier, you may want to emerge the <c>module-rebuild</c> package, which will
-keep track of module packages and rebuild them for you. First run <c>module
-rebuild populate</c> to create the list, and then after every kernel
+keep track of module packages and rebuild them for you. First run
+<c>module-rebuild populate</c> to create the list, and then after every kernel
 (re)compile, you just run <c>module-rebuild rebuild</c>, and your external
 modules will be rebuilt.
 </impo>



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



             reply	other threads:[~2007-01-31 16:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 16:39 Josh Saddler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-05  9:16 [gentoo-doc-cvs] cvs commit: alsa-guide.xml Joshua Saddler
2007-05-19  3:00 Josh Saddler
2007-05-07  7:08 Josh Saddler
2007-05-06 23:27 Josh Saddler
2007-05-03  6:21 Josh Saddler
2007-03-10 13:02 Jan Kundrat
2007-02-17 19:03 Josh Saddler
2007-01-31 15:54 Josh Saddler
2006-11-02 18:24 Josh Saddler
2006-07-07 14:40 Lukasz Damentko
2006-07-06 19:51 Lukasz Damentko
2006-05-27 13:59 Xavier Neys
2006-05-01  5:52 Shyam Mani
2006-03-25  6:59 Shyam Mani
2006-01-01 11:51 Xavier Neys
2005-10-30 16:02 Shyam Mani
2005-09-10 18:02 swift
2005-09-09  6:49 Shyam Mani
2005-08-30 11:38 Shyam Mani
2005-07-26 17:28 Marcelo Goes
2005-07-16 11:45 Alin Dobre
2005-07-14 19:22 Shyam Mani
2005-07-14  9:11 Xavier Neys
2005-07-14  9:05 Sven Vermeulen
2005-07-12 19:17 Shyam Mani

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=E1HCIUY-0006DD-OF@lark.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