@matheusbsbs / matheus-bagliano / commits / 3a9f1a55ee
Fork 0

cvs-migration document: make the need for "push" more obvious

It really is an important concept to grasp for people coming from CVS. Even if it is briefly mentioned, it is not obvious enough to sink in. [jc: with wording updates from J. Bruce Fields] Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de> Signed-off-by: Junio C Hamano <junkio@cox.net>

Johannes Schindelin committed Dec 6, 2006 at 13:27 UTC 3a9f1a55eec9cc508abccda6a3fee795b812d66d
1 file changed +5
Documentation/cvs-migration.txt
+5
@@ -24,6 +24,11 @@ First, note some ways that git differs from CVS:
24 single shared repository which people can synchronize with; see below
25 for details.
26
27 + * Since every working tree contains a repository, a commit in your
28 + private repository will not publish your changes; it will only create
29 + a revision. You have to "push" your changes to a public repository to
30 + make them visible to others.
31 +
32 Importing a CVS archive
33 -----------------------
34