From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/doc/en: xorg-config.xml
Date: Sun, 23 May 2010 21:29:35 +0000 (UTC) [thread overview]
Message-ID: <20100523212935.C65792CCD4@corvid.gentoo.org> (raw)
nightmorph 10/05/23 21:29:35
Modified: xorg-config.xml
Log:
Fix estonian layout bzcat command, bug 321093
Revision Changes Path
1.38 xml/htdocs/doc/en/xorg-config.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/xorg-config.xml?rev=1.38&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/xorg-config.xml?rev=1.38&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/xorg-config.xml?r1=1.37&r2=1.38
Index: xorg-config.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- xorg-config.xml 16 Mar 2010 20:07:43 -0000 1.37
+++ xorg-config.xml 23 May 2010 21:29:35 -0000 1.38
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v 1.37 2010/03/16 20:07:43 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v 1.38 2010/05/23 21:29:35 nightmorph Exp $ -->
<guide>
<title>The X Server Configuration HOWTO</title>
@@ -22,8 +22,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.27</version>
-<date>2010-03-16</date>
+<version>1.28</version>
+<date>2010-05-23</date>
<chapter>
<title>What is the X Window Server?</title>
@@ -550,7 +550,7 @@
</p>
<pre caption="Using an existing config file">
-# <i>bzcat /usr/share/doc/hal-*/*/use-estonian-layout.fdi > /etc/hal/fdi/policy/10-xinput-configuration.fdi</i>
+# <i>bzcat /usr/share/doc/hal-*/*/use-estonian-layout.fdi.bz2 > /etc/hal/fdi/policy/10-xinput-configuration.fdi</i>
</pre>
<p>
next reply other threads:[~2010-05-23 21:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 21:29 Joshua Saddler (nightmorph) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-01 18:24 [gentoo-commits] gentoo commit in xml/htdocs/doc/en: xorg-config.xml Sven Vermeulen (swift)
2012-06-14 6:48 Joshua Saddler (nightmorph)
2011-09-02 19:07 Sven Vermeulen (swift)
2011-08-23 15:04 Sven Vermeulen (swift)
2011-08-23 14:43 Sven Vermeulen (swift)
2011-03-23 9:03 Joshua Saddler (nightmorph)
2011-03-02 8:16 Joshua Saddler (nightmorph)
2011-03-02 7:17 Joshua Saddler (nightmorph)
2010-10-25 7:38 Joshua Saddler (nightmorph)
2010-10-12 23:13 Joshua Saddler (nightmorph)
2010-08-29 3:39 Joshua Saddler (nightmorph)
2010-05-23 21:31 Joshua Saddler (nightmorph)
2010-03-16 20:07 Joshua Saddler (nightmorph)
2010-01-02 3:02 Joshua Saddler (nightmorph)
2009-12-31 1:37 Joshua Saddler (nightmorph)
2009-12-17 4:41 Joshua Saddler (nightmorph)
2009-12-17 4:37 Joshua Saddler (nightmorph)
2009-12-09 1:35 Joshua Saddler (nightmorph)
2009-10-02 7:37 Joshua Saddler (nightmorph)
2009-06-10 18:28 Joshua Saddler (nightmorph)
2009-01-26 8:08 Joshua Saddler (nightmorph)
2008-11-10 7:01 Joshua Saddler (nightmorph)
2008-05-23 19:40 Sven Vermeulen (swift)
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=20100523212935.C65792CCD4@corvid.gentoo.org \
--to=nightmorph@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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