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 <bfields@citi.umich.edu> Signed-off-by: Junio C Hamano <junkio@cox.net>
J. Bruce Fields committed
Dec 31, 2006 at 18:47 UTC
c04197ee1e575cf78662b2c8c055089a5c669214
1 file changed
+4
-7
Documentation/cvs-migration.txt
+4
-7
@@ -34,13 +34,10 @@ them first before running git pull.
34
35
[NOTE]
36
================================
37
-The first `git clone` places the following in the
38
-`my-project/.git/remotes/origin` file, and that's why the previous step
39
-and the next step both work.
40
-------------
41
-URL: foo.com:/pub/project.git/
42
-Pull: refs/heads/master:refs/remotes/origin/master
43
-------------
37
+The `pull` command knows where to get updates from because of certain
38
+configuration variables that were set by the first `git clone`
39
+command; see `git repo-config -l` and the gitlink:git-repo-config[1] man
40
+page for details.
41
================================
42
43
You can update the shared repository with your changes by first committing