From: Johannes Schindelin Date: Wed, 06 Dec 2006 12:27:40 GMT Subject: [PATCH] cvs-migration document: make the need for "push" more obvious Message-ID: In-Reply-To: <20061206.105251.144349770.wl@gnu.org> 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. Signed-off-by: Johannes Schindelin --- On Wed, 6 Dec 2006, Werner LEMBERG wrote: > It took me a while to realize that a git repository, as soon as > you've cloned it, is *self-contained*, and that commiting to the > repository and synchronizing with a different git repository are > two completely different things (contrary to CVS). This should > be pronounced more in the CVS->git guide. Documentation/cvs-migration.txt | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/Documentation/cvs-migration.txt b/Documentation/cvs-migration.txt index 6812683..8e610c7 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 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 ----------------------- --