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: gentoo-kernel.xml
Date: Mon, 18 Dec 2006 11:53:12 +0000	[thread overview]
Message-ID: <20061218115312.99DF264850@smtp.gentoo.org> (raw)

nightmorph    06/12/18 11:53:12

  Modified:             gentoo-kernel.xml
  Log:
  minor typo fixes, **no content change**

Revision  Changes    Path
1.48                 xml/htdocs/doc/en/gentoo-kernel.xml

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

Index: gentoo-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-kernel.xml,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- gentoo-kernel.xml	5 Dec 2006 00:08:44 -0000	1.47
+++ gentoo-kernel.xml	18 Dec 2006 11:53:12 -0000	1.48
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-kernel.xml,v 1.47 2006/12/05 00:08:44 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-kernel.xml,v 1.48 2006/12/18 11:53:12 nightmorph Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 <guide link="/doc/en/gentoo-kernel.xml">
@@ -28,7 +28,7 @@
 <author title="Editor">
   <mail link="fox2mike@gentoo.org">Shyam Mani</mail>
 </author>
-<author title="editor">
+<author title="Editor">
   <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
 </author>
 
@@ -177,10 +177,11 @@
 <body>
 
 <p>
-<c>hppa-sources</c>, <c>mips-sources</c>, <c>sh-sources</c> <c>sparc-sources</c>
-and <c>xbox-sources</c> are, as their names suggest, patched to run best on
-specific architectures. They also contain some of the patches for hardware and
-features support from the other patch sets mentioned above and below.
+<c>hppa-sources</c>, <c>mips-sources</c>, <c>sh-sources</c>,
+<c>sparc-sources</c>, and <c>xbox-sources</c> are, as their names suggest,
+patched to run best on specific architectures. They also contain some of the
+patches for hardware and features support from the other patch sets mentioned
+above and below.
 </p>
 
 </body>



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



             reply	other threads:[~2006-12-18 11:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18 11:53 Josh Saddler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-23 20:46 [gentoo-doc-cvs] cvs commit: gentoo-kernel.xml Sven Vermeulen
2008-02-03 18:30 Sven Vermeulen
2008-02-03 18:28 Sven Vermeulen
2008-02-03 14:42 Xavier Neys
2006-12-04  1:19 Josh Saddler
2006-11-30 20:08 Josh Saddler
2006-09-06 14:49 vapier
2006-07-18 15:40 Lukasz Damentko
2006-07-03 19:17 Shyam Mani
2006-01-31  1:15 Flammie Pirinen
2006-01-30  2:42 Marcelo Goes
2006-01-13 19:17 Jan Kundrat
2006-01-13 19:16 Jan Kundrat
2006-01-13  9:57 Shyam Mani
2005-07-26 18:07 Alin Dobre
2005-07-06 15:30 Sven Vermeulen

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=20061218115312.99DF264850@smtp.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