Autogenerated HTML docs for v1.4.4.2-gde51

diff --git a/cvs-migration.html b/cvs-migration.html
index fbcb5501eb66b02db30bf96b446a222ac98f1e7b..af8d20547bbfd74715d026737c8f66a6f6528d53 100644 (file)
--- a/cvs-migration.html
+++ b/cvs-migration.html
@@ -296,6 +296,14 @@ Every working tree contains a repository with a full copy of the
     for details.\r
 </p>\r
 </li>\r
+<li>\r
+<p>\r
+Since every working tree contains a repository, a commit in your\r
+    private repository will not publish your changes; it will only create\r
+    a revision. You have to "push" your changes to a public repository to\r
+    make them visible to others.\r
+</p>\r
+</li>\r
 </ul>\r
 </div>\r
 </div>\r
@@ -343,7 +351,7 @@ variants of this model.</p>
 <p>With a small group, developers may just pull changes from each other's\r
 repositories without the need for a central maintainer.</p>\r
 </div>\r
-<h2>Emulating the CVS Development Model</h2>\r
+<h2>Creating a Shared Repository</h2>\r
 <div class="sectionbody">\r
 <p>Start with an ordinary git working directory containing the project, and\r
 remove the checked-out files, keeping just the bare .git directory:</p>\r
@@ -367,7 +375,10 @@ $ GIT_DIR=repo.git git repo-config core.sharedrepository true</tt></pre>
 </div></div>\r
 <p>Make sure committers have a umask of at most 027, so that the directories\r
 they create are writable and searchable by other group members.</p>\r
-<p>Suppose this repository is now set up in /pub/repo.git on the host\r
+</div>\r
+<h2>Performing Development on a Shared Repository</h2>\r
+<div class="sectionbody">\r
+<p>Suppose a repository is now set up in /pub/repo.git on the host\r
 foo.com.  Then as an individual committer you can clone the shared\r
 repository:</p>\r
 <div class="listingblock">\r
@@ -399,14 +410,16 @@ Pull: master:origin</tt></pre>
 </td>\r
 </tr></table>\r
 </div>\r
-<p>You can update the shared repository with your changes using:</p>\r
+<p>You can update the shared repository with your changes by first commiting\r
+your changes, and then using:</p>\r
 <div class="listingblock">\r
 <div class="content">\r
 <pre><tt>$ git push origin master</tt></pre>\r
 </div></div>\r
-<p>If someone else has updated the repository more recently, <tt>git push</tt>, like\r
-<tt>cvs commit</tt>, will complain, in which case you must pull any changes\r
-before attempting the push again.</p>\r
+<p>to "push" those commits to the shared repository.  If someone else has\r
+updated the repository more recently, <tt>git push</tt>, like <tt>cvs commit</tt>, will\r
+complain, in which case you must pull any changes before attempting the\r
+push again.</p>\r
 <p>In the <tt>git push</tt> command above we specify the name of the remote branch\r
 to update (<tt>master</tt>).  If we leave that out, <tt>git push</tt> tries to update\r
 any branches in the remote repository that have the same name as a branch\r
@@ -579,7 +592,7 @@ that contain this changed "if" statement:</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 03-Oct-2006 08:41:45 UTC\r
+Last updated 06-Dec-2006 21:11:42 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/cvs-migration.txt b/cvs-migration.txt
index 6812683a16852ea165dff7dd0582b53138e3f12c..a436180dd417f39b812d54df5168c89b501d5193 100644 (file)
--- a/cvs-migration.txt
+++ b/cvs-migration.txt
@@ -24,6 +24,11 @@ First, note some ways that git differs from CVS:
     single shared repository which people can synchronize with; see below
     for details.
 
+  * Since every working tree contains a repository, a commit in your
+    private repository will not publish your changes; it will only create
+    a revision. You have to "push" your changes to a public repository to
+    make them visible to others.
+
 Importing a CVS archive
 -----------------------
 
@@ -76,8 +81,8 @@ variants of this model.
 With a small group, developers may just pull changes from each other's
 repositories without the need for a central maintainer.
 
-Emulating the CVS Development Model
------------------------------------
+Creating a Shared Repository
+----------------------------
 
 Start with an ordinary git working directory containing the project, and
 remove the checked-out files, keeping just the bare .git directory:
@@ -105,7 +110,10 @@ $ GIT_DIR=repo.git git repo-config core.sharedrepository true
 Make sure committers have a umask of at most 027, so that the directories
 they create are writable and searchable by other group members.
 
-Suppose this repository is now set up in /pub/repo.git on the host
+Performing Development on a Shared Repository
+---------------------------------------------
+
+Suppose a repository is now set up in /pub/repo.git on the host
 foo.com.  Then as an individual committer you can clone the shared
 repository:
 
@@ -134,15 +142,17 @@ Pull: master:origin
 ------------
 ================================
 
-You can update the shared repository with your changes using:
+You can update the shared repository with your changes by first commiting
+your changes, and then using:
 
 ------------------------------------------------
 $ git push origin master
 ------------------------------------------------
 
-If someone else has updated the repository more recently, `git push`, like
-`cvs commit`, will complain, in which case you must pull any changes
-before attempting the push again.
+to "push" those commits to the shared repository.  If someone else has
+updated the repository more recently, `git push`, like `cvs commit`, will
+complain, in which case you must pull any changes before attempting the
+push again.
 
 In the `git push` command above we specify the name of the remote branch
 to update (`master`).  If we leave that out, `git push` tries to update