From: Sven Vermeulen <swift@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: devfs-guide.xml
Date: Fri, 23 May 2008 19:52:53 +0000 [thread overview]
Message-ID: <E1JzdJt-0000vF-FS@stork.gentoo.org> (raw)
swift 08/05/23 19:52:53
Modified: devfs-guide.xml
Log:
Coding style
Revision Changes Path
1.17 xml/htdocs/doc/en/devfs-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/devfs-guide.xml?rev=1.17&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/devfs-guide.xml?rev=1.17&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/devfs-guide.xml?r1=1.16&r2=1.17
Index: devfs-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/devfs-guide.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- devfs-guide.xml 16 Nov 2007 10:28:01 -0000 1.16
+++ devfs-guide.xml 23 May 2008 19:52:53 -0000 1.17
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/devfs-guide.xml,v 1.16 2007/11/16 10:28:01 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/devfs-guide.xml,v 1.17 2008/05/23 19:52:53 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -160,7 +160,7 @@
aren't really visible, but for the kernel maintainers the problems are big
enough to mark devfs <e>obsolete</e> in favor of <uri
link="udev-guide.xml">udev</uri>, which Gentoo supports and uses by default on
-most architectures since the 2005.0 release when using a 2.6 kernel.
+most architectures since the 2005.0 release when using a 2.6 kernel.
</p>
<p>
@@ -191,7 +191,7 @@
For instance, all IDE-related devices are inside the
<path>/dev/ide/</path> device directory, and SCSI-related devices are inside
<path>/dev/scsi/</path>. SCSI and IDE disks are seen in the same way,
-meaning they both have the same subdirectory structure.
+meaning they both have the same subdirectory structure.
</p>
<p>
@@ -297,7 +297,7 @@
<body>
<warn>
-Currently, Gentoo cannot live without the compatibility symlinks.
+Currently, Gentoo cannot live without the compatibility symlinks.
</warn>
<p>
@@ -348,7 +348,7 @@
has the final word on permissions. You shouldn't be using pam_console anyway, as
it has been <uri
link="http://www.gentoo.org/proj/en/base/pam/upgrade-0.99.xml">removed from
-Portage</uri>.
+Portage</uri>.
</impo>
<p>
--
gentoo-doc-cvs@lists.gentoo.org mailing list
next reply other threads:[~2008-05-23 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 19:52 Sven Vermeulen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-16 10:28 [gentoo-doc-cvs] cvs commit: devfs-guide.xml Jan Kundrat
2007-11-15 22:41 Josh Saddler
2005-07-21 15:30 Xavier Neys
2005-07-18 10:03 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=E1JzdJt-0000vF-FS@stork.gentoo.org \
--to=swift@stork.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