Autogenerated HTML docs for v1.8.1.2-545-g2f19ad

1 files changed, 15 insertions, 15 deletions

diff --git a/git-cvsserver.html b/git-cvsserver.html
index 053e558aa..61ee476d9 100644
--- a/git-cvsserver.html
+++ b/git-cvsserver.html
@@ -737,7 +737,7 @@ git-cvsserver(1) Manual Page
 <h2>NAME</h2>

 <div class="sectionbody">

 <p>git-cvsserver -

-   A CVS server emulator for git

+   A CVS server emulator for Git

 </p>

 </div>

 </div>

@@ -837,7 +837,7 @@ unless <em>--export-all</em> was given, too.
 <div class="sect1">

 <h2 id="_description">DESCRIPTION</h2>

 <div class="sectionbody">

-<div class="paragraph"><p>This application is a CVS emulation layer for git.</p></div>

+<div class="paragraph"><p>This application is a CVS emulation layer for Git.</p></div>

 <div class="paragraph"><p>It is highly functional. However, not all methods are implemented,

 and for those methods that are implemented,

 not all switches are implemented.</p></div>

@@ -848,8 +848,8 @@ plugin. Most functionality works fine with both of these clients.</p></div>
 <div class="sect1">

 <h2 id="_limitations">LIMITATIONS</h2>

 <div class="sectionbody">

-<div class="paragraph"><p>CVS clients cannot tag, branch or perform GIT merges.</p></div>

-<div class="paragraph"><p><em>git-cvsserver</em> maps GIT branches to CVS modules. This is very different

+<div class="paragraph"><p>CVS clients cannot tag, branch or perform Git merges.</p></div>

+<div class="paragraph"><p><em>git-cvsserver</em> maps Git branches to CVS modules. This is very different

 from what most CVS users would expect since in CVS modules usually represent

 one or more directories.</p></div>

 </div>

@@ -906,7 +906,7 @@ library&#8217;s crypt() function, so don&#8217;t use the -m option.</p></div>
 <div class="content">

 <pre><code>   cvs -d:pserver:someuser:somepassword &lt;at&gt; server/path/repo.git co &lt;HEAD_name&gt;</code></pre>

 </div></div>

-<div class="paragraph"><p>No special setup is needed for SSH access, other than having GIT tools

+<div class="paragraph"><p>No special setup is needed for SSH access, other than having Git tools

 in the PATH. If you have clients that do not accept the CVS_SERVER

 environment variable, you can rename <em>git-cvsserver</em> to <code>cvs</code>.</p></div>

 <div class="paragraph"><p>Note: Newer CVS versions (&gt;= 1.12.11) also support specifying

@@ -939,8 +939,8 @@ For each repo that you want accessible from CVS you need to edit config in
 <div class="paragraph"><p>Note: you need to ensure each user that is going to invoke <em>git-cvsserver</em> has

 write access to the log file and to the database (see

 <a href="#dbbackend">Database Backend</a>. If you want to offer write access over

-SSH, the users of course also need write access to the git repository itself.</p></div>

-<div class="paragraph"><p>You also need to ensure that each repository is "bare" (without a git index

+SSH, the users of course also need write access to the Git repository itself.</p></div>

+<div class="paragraph"><p>You also need to ensure that each repository is "bare" (without a Git index

 file) for <code>cvs commit</code> to work. See <a href="gitcvs-migration.html">gitcvs-migration(7)</a>.</p></div>

 <div class="paragraph" id="configaccessmethod"><p>All configuration variables can also be overridden for a specific method of

 access. Valid method names are "ext" (for SSH access) and "pserver". The

@@ -961,7 +961,7 @@ allowing access over SSH.</p></div>
 If you didn&#8217;t specify the CVSROOT/CVS_SERVER directly in the checkout command,

    automatically saving it in your <em>CVS/Root</em> files, then you need to set them

    explicitly in your environment.  CVSROOT should be set as per normal, but the

-   directory should point at the appropriate git repo.  As above, for SSH clients

+   directory should point at the appropriate Git repo.  As above, for SSH clients

    <em>not</em> restricted to <em>git-shell</em>, CVS_SERVER should be set to <em>git-cvsserver</em>.

 </p>

 <div class="openblock">

@@ -985,7 +985,7 @@ For SSH clients that will make commits, make sure their server-side
 <li>

 <p>

 Clients should now be able to check out the project. Use the CVS <em>module</em>

-   name to indicate what GIT <em>head</em> you want to check out.  This also sets the

+   name to indicate what Git <em>head</em> you want to check out.  This also sets the

    name of your newly checked-out directory, unless you tell it otherwise with

    <code>-d &lt;dir_name&gt;</code>.  For example, this checks out <em>master</em> branch to the

    <code>project-master</code> directory:

@@ -1001,7 +1001,7 @@ Clients should now be able to check out the project. Use the CVS <em>module</em>
 <div class="sect1">

 <h2 id="dbbackend">Database Backend</h2>

 <div class="sectionbody">

-<div class="paragraph"><p><em>git-cvsserver</em> uses one database per git head (i.e. CVS module) to

+<div class="paragraph"><p><em>git-cvsserver</em> uses one database per Git head (i.e. CVS module) to

 store information about the repository to maintain consistent

 CVS revision numbers. The database needs to be

 updated (i.e. written to) after every commit.</p></div>

@@ -1013,7 +1013,7 @@ access method and requested operation.</p></div>
 the pserver method), <em>git-cvsserver</em> should have write access to

 the database to work reliably (otherwise you need to make sure

 that the database is up-to-date any time <em>git-cvsserver</em> is executed).</p></div>

-<div class="paragraph"><p>By default it uses SQLite databases in the git directory, named

+<div class="paragraph"><p>By default it uses SQLite databases in the Git directory, named

 <code>gitcvs.&lt;module_name&gt;.sqlite</code>. Note that the SQLite backend creates

 temporary files in the same directory as the database file on

 write so it might not be enough to grant the users using

@@ -1104,7 +1104,7 @@ gitcvs.dbTableNamePrefix
 </dt>

 <dd>

 <p>

-        git directory name

+        Git directory name

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1112,7 +1112,7 @@ gitcvs.dbTableNamePrefix
 </dt>

 <dd>

 <p>

-        git directory name, where all characters except for

+        Git directory name, where all characters except for

         alpha-numeric ones, <code>.</code>, and <code>-</code> are replaced with

         <code>_</code> (this should make it easier to use the directory

         name in a filename if wanted)

@@ -1123,7 +1123,7 @@ gitcvs.dbTableNamePrefix
 </dt>

 <dd>

 <p>

-        CVS module/git head name

+        CVS module/Git head name

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1309,7 +1309,7 @@ and <code>gitcvs.allbinary</code> to "guess".</p></div>
 <div id="footnotes"><hr /></div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2013-01-25 13:32:06 PST

+Last updated 2013-02-05 21:07:26 PST

 </div>

 </div>

 </body>