From: Sven Vermeulen <swift@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: vi-guide.xml
Date: Mon, 19 May 2008 19:59:02 +0000 [thread overview]
Message-ID: <E1JyBVe-0004y5-Jz@stork.gentoo.org> (raw)
swift 08/05/19 19:59:02
Modified: vi-guide.xml
Log:
Damn, missed one - trailing whitespace
Revision Changes Path
1.16 xml/htdocs/doc/en/vi-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vi-guide.xml?rev=1.16&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vi-guide.xml?rev=1.16&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vi-guide.xml?r1=1.15&r2=1.16
Index: vi-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/vi-guide.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- vi-guide.xml 19 May 2008 19:57:20 -0000 1.15
+++ vi-guide.xml 19 May 2008 19:59:02 -0000 1.16
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vi-guide.xml,v 1.15 2008/05/19 19:57:20 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vi-guide.xml,v 1.16 2008/05/19 19:59:02 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/vi-guide.xml">
@@ -135,7 +135,7 @@
<p>
If you have vim installed, type <c>vim myfile.txt</c>. If you'd prefer to
-use gvim, type <c>gvim myfile.txt</c>. <path>myfile.txt</path> should be the
+use gvim, type <c>gvim myfile.txt</c>. <path>myfile.txt</path> should be the
name of a text file on your system.
</p>
--
gentoo-doc-cvs@lists.gentoo.org mailing list
next reply other threads:[~2008-05-19 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 19:59 Sven Vermeulen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-19 19:57 [gentoo-doc-cvs] cvs commit: vi-guide.xml Sven Vermeulen
2005-07-21 15:58 Xavier Neys
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=E1JyBVe-0004y5-Jz@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