[gentoo-doc-cvs] cvs commit: alsa-guide.xml

[Josh Saddler]

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@g.o mailing list