path: root/Documentation/cvs-migration.txt
diff options
authorJohannes Schindelin <>2006-12-06 12:27:40 (GMT)
committerJunio C Hamano <>2006-12-06 17:52:57 (GMT)
commit3a9f1a55eec9cc508abccda6a3fee795b812d66d (patch)
tree5b076ab1ace6b5c0d624e60592e68ac2de4b3d27 /Documentation/cvs-migration.txt
parent8ebe185bbf3f1f4f59bcc61e3d1849a76f6af983 (diff)
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 <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/cvs-migration.txt')
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/cvs-migration.txt b/Documentation/cvs-migration.txt
index 6812683..9c2a395 100644
--- a/Documentation/cvs-migration.txt
+++ b/Documentation/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