texi2html-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Texi2html-cvs] Changes to texi2html/Tests/ccvs_res/cvs_2.html


From: Patrice Dumas
Subject: [Texi2html-cvs] Changes to texi2html/Tests/ccvs_res/cvs_2.html
Date: Tue, 23 Aug 2005 19:51:22 -0400

Index: texi2html/Tests/ccvs_res/cvs_2.html
diff -u texi2html/Tests/ccvs_res/cvs_2.html:1.23 
texi2html/Tests/ccvs_res/cvs_2.html:1.24
--- texi2html/Tests/ccvs_res/cvs_2.html:1.23    Tue Aug  9 17:19:21 2005
+++ texi2html/Tests/ccvs_res/cvs_2.html Tue Aug 23 23:51:10 2005
@@ -11,10 +11,10 @@
 
 -->
 <head>
-<title>CVS--Concurrent Versions System v1.12.1.1: 2. The Repository</title>
+<title>CVS&mdash;Concurrent Versions System v1.12.1.1: 2. The 
Repository</title>
 
-<meta name="description" content="CVS--Concurrent Versions System v1.12.1.1: 
2. The Repository">
-<meta name="keywords" content="CVS--Concurrent Versions System v1.12.1.1: 2. 
The Repository">
+<meta name="description" content="CVS&mdash;Concurrent Versions System 
v1.12.1.1: 2. The Repository">
+<meta name="keywords" content="CVS&mdash;Concurrent Versions System v1.12.1.1: 
2. The Repository">
 <meta name="resource-type" content="document">
 <meta name="distribution" content="global">
 <meta name="Generator" content="texi2html">
@@ -340,7 +340,7 @@
 <cite>rcsfile(5)</cite>, distributed with <small>RCS</small>, or the
 file <tt>`doc/RCSFILES'</tt> in the <small>CVS</small> source
 distribution.  This
-file format has become very common--many systems other
+file format has become very common&mdash;many systems other
 than <small>CVS</small> or <small>RCS</small> can at least import history
 files in this format.
 </p>
@@ -348,7 +348,7 @@
 ways from the standard format.  The biggest difference
 is magic branches; for more information see <a href="cvs_5.html#SEC59">Magic 
branch numbers</a>.  Also in <small>CVS</small> the valid tag names
 are a subset of what <small>RCS</small> accepts; for <small>CVS</small>'s
-rules see <a href="cvs_4.html#SEC48">Tags-Symbolic revisions</a>.
+rules see <a href="cvs_4.html#SEC48">Tags&ndash;Symbolic revisions</a>.
 </p>
 <hr size="6">
 <a name="File-permissions"></a>
@@ -1518,7 +1518,7 @@
 <h3 class="subsection"> 2.9.1 Server requirements </h3>
 
 <p>The quick answer to what sort of machine is suitable as
-a server is that requirements are modest--a server
+a server is that requirements are modest&mdash;a server
 with 32M of memory or even less can handle a fairly
 large source tree with a fair amount of activity.
 </p>
@@ -1564,7 +1564,7 @@
 time.
 </p>
 <p>Resource consumption for the client is even more
-modest--any machine with enough capacity to run the
+modest&mdash;any machine with enough capacity to run the
 operating system in question should have little
 trouble.
 </p>
@@ -1814,7 +1814,7 @@
 <a name="IDX82"></a>
 <a name="IDX83"></a>
 <p>Because the client stores and transmits passwords in
-cleartext (almost--see <a href="#SEC32">Security considerations with password 
authentication</a>, for details), a separate <small>CVS</small> password
+cleartext (almost&mdash;see <a href="#SEC32">Security considerations with 
password authentication</a>, for details), a separate <small>CVS</small> 
password
 file is generally used, so people don't compromise
 their regular passwords when they access the
 repository.  This file is
@@ -2075,7 +2075,7 @@
 <tt>`$HOME/.cvspass'</tt>.  That file's format is
 human-readable, and to a degree human-editable, but
 note that the passwords are not stored in
-cleartext--they are trivially encoded to protect them
+cleartext&mdash;they are trivially encoded to protect them
 from &quot;innocent&quot; compromise (i.e., inadvertent viewing
 by a system administrator or other non-malicious
 person).
@@ -2385,7 +2385,7 @@
 </p>
 <p>        A user who has read-only access can do only
 those <small>CVS</small> operations which do not modify the
-repository, except for certain &quot;administrative&quot; files
+repository, except for certain &ldquo;administrative&rdquo; files
 (such as lock files and the history file).  It may be
 desirable to use this feature in conjunction with
 user-aliasing (see section <a href="#SEC30">Setting up the server for password 
authentication</a>).
@@ -2416,7 +2416,7 @@
 <p>        (Don't forget the newline after the last user.)
 </p>
 <p>        &quot;Exclusion&quot; means explicitly listing everyone
-who has <em>write</em> access--if the file
+who has <em>write</em> access&mdash;if the file
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">$CVSROOT/CVSROOT/writers
 </pre></td></tr></table>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]