[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Texi2html-cvs] Changes to texi2html/Tests/ccvs_res/cvs_1.html
From: |
Patrice Dumas |
Subject: |
[Texi2html-cvs] Changes to texi2html/Tests/ccvs_res/cvs_1.html |
Date: |
Tue, 23 Aug 2005 19:51:20 -0400 |
Index: texi2html/Tests/ccvs_res/cvs_1.html
diff -u texi2html/Tests/ccvs_res/cvs_1.html:1.22
texi2html/Tests/ccvs_res/cvs_1.html:1.23
--- texi2html/Tests/ccvs_res/cvs_1.html:1.22 Tue Aug 9 17:19:21 2005
+++ texi2html/Tests/ccvs_res/cvs_1.html Tue Aug 23 23:51:10 2005
@@ -11,10 +11,10 @@
-->
<head>
-<title>CVS--Concurrent Versions System v1.12.1.1: 1. Overview</title>
+<title>CVS—Concurrent Versions System v1.12.1.1: 1. Overview</title>
-<meta name="description" content="CVS--Concurrent Versions System v1.12.1.1:
1. Overview">
-<meta name="keywords" content="CVS--Concurrent Versions System v1.12.1.1: 1.
Overview">
+<meta name="description" content="CVS—Concurrent Versions System
v1.12.1.1: 1. Overview">
+<meta name="keywords" content="CVS—Concurrent Versions System v1.12.1.1:
1. Overview">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2html">
@@ -255,7 +255,7 @@
<dd>
<p>When faced with conflicts within a single file, most
developers manage to resolve them without too much
-effort. But a more general definition of "conflict"
+effort. But a more general definition of “conflict”
includes problems too difficult to solve without
communication between developers.
</p>
@@ -455,7 +455,7 @@
</pre></td></tr></table>
<p><small>CVS</small> starts an editor, to allow you to enter a log
-message. You type in "Added an optimization pass.",
+message. You type in “Added an optimization pass.”,
save the temporary file, and exit the editor.
</p>
<a name="IDX9"></a>
@@ -484,7 +484,7 @@
had when it was last gotten or updated. Therefore, if
a file's modification time has changed but its contents
have not, it will show up as modified. The simplest
-way to handle this is simply not to worry about it--if
+way to handle this is simply not to worry about it—if
you proceed with the commit <small>CVS</small> will detect that
the contents are not modified and treat it as an
unmodified file. The next <code>update</code> will clue
@@ -527,7 +527,7 @@
$ rm -r tc
</pre></td></tr></table>
-<p>but a better way is to use the <code>release</code> command (see section <a
href="cvs_16.html#SEC149">release--Indicate that a Module is no longer in
use</a>):
+<p>but a better way is to use the <code>release</code> command (see section <a
href="cvs_16.html#SEC149">release—Indicate that a Module is no longer in
use</a>):
</p>
<table><tr><td> </td><td><pre class="example">$ cd ..
$ cvs release -d tc