public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alin Dobre" <alin@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: migration-to-2.6.xml
Date: Sat, 10 Sep 2005 11:53:14 +0000	[thread overview]
Message-ID: <200509101149.j8ABnNdc001765@robin.gentoo.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]

alin        05/09/10 11:53:14

  Modified:    xml/htdocs/doc/en migration-to-2.6.xml
  Log:
  fixed Michal's name, again. thanks to rane for pointing the correct character

Revision  Changes    Path
1.23      +4 -4      xml/htdocs/doc/en/migration-to-2.6.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/migration-to-2.6.xml?rev=1.23&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/migration-to-2.6.xml?rev=1.23&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/migration-to-2.6.xml.diff?r1=1.22&r2=1.23&cvsroot=gentoo

Index: migration-to-2.6.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/migration-to-2.6.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- migration-to-2.6.xml	10 Sep 2005 11:31:51 -0000	1.22
+++ migration-to-2.6.xml	10 Sep 2005 11:53:14 -0000	1.23
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/migration-to-2.6.xml,v 1.22 2005/09/10 11:31:51 alin Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/migration-to-2.6.xml,v 1.23 2005/09/10 11:53:14 alin Exp $ -->
 
 <guide link="/doc/en/migration-to-2.6.xml">
 
@@ -28,7 +28,7 @@
 2.6, devfs to udev, OSS to ALSA, and LVM to LVM2.
 </abstract>
 
-<version>0.2.10</version>
+<version>0.2.11</version>
 <date>2005-09-10</date>
 
 <chapter>
@@ -660,9 +660,9 @@
 
 <p>
 The developer of bootsplash appears to have lost interest in his project, given
-some design problems. However, Gentoo developer <e>MichaÅ Januszewski</e> is
+some design problems. However, Gentoo developer <e>Michał Januszewski</e> is
 developing a successor, <c>gensplash</c>, which in included in the
-gentoo-sources-2.6 kernel. You can follow MichaÅ's <uri
+gentoo-sources-2.6 kernel. You can follow Michał's <uri
 link="http://dev.gentoo.org/~spock/projects/gensplash/archive/gensplash-in-5-easy-steps.txt">
 Gensplash in 5 easy steps</uri> document in order to familiarize yourself with
 how gensplash is operated.



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



             reply	other threads:[~2005-09-10 11:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10 11:53 Alin Dobre [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-02  0:33 [gentoo-doc-cvs] cvs commit: migration-to-2.6.xml Joshua Saddler
2008-01-02  0:24 Joshua Saddler
2005-09-10 11:31 Alin Dobre
2005-09-08 10:32 Shyam Mani
2005-09-08 10:10 Shyam Mani
2005-09-08 10:08 Shyam Mani
2005-08-25  0:52 vapier

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=200509101149.j8ABnNdc001765@robin.gentoo.org \
    --to=alin@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