path: root/Documentation/cvs-migration.txt
diff options
authorJ. Bruce Fields <>2006-12-31 23:47:33 (GMT)
committerJunio C Hamano <>2007-01-01 00:15:12 (GMT)
commitc04197ee1e575cf78662b2c8c055089a5c669214 (patch)
treee114035bce031baf6a2f733f3d728f1040453e55 /Documentation/cvs-migration.txt
parent0ae5f98c7ba29fa4c698989cd6b38deba06d5bf3 (diff)
Docs: update cvs-migration.txt to reflect clone's new default behavior
I couldn't think of a really quick way to give all the details, so just refer readers to the git-repo-config man page instead. I haven't tested recent cvs import behavior--some time presumably it should be updated to do something more similar to clone. Signed-off-by: J. Bruce Fields <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/cvs-migration.txt')
1 files changed, 4 insertions, 7 deletions
diff --git a/Documentation/cvs-migration.txt b/Documentation/cvs-migration.txt
index b657f45..8e09bea 100644
--- a/Documentation/cvs-migration.txt
+++ b/Documentation/cvs-migration.txt
@@ -34,13 +34,10 @@ them first before running git pull.
-The first `git clone` places the following in the
-`my-project/.git/remotes/origin` file, and that's why the previous step
-and the next step both work.
-Pull: refs/heads/master:refs/remotes/origin/master
+The `pull` command knows where to get updates from because of certain
+configuration variables that were set by the first `git clone`
+command; see `git repo-config -l` and the gitlink:git-repo-config[1] man
+page for details.
You can update the shared repository with your changes by first committing