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>
This commit is contained in:
parent
0ae5f98c7b
commit
c04197ee1e
@ -34,13 +34,10 @@ them first before running git pull.
|
|||||||
|
|
||||||
[NOTE]
|
[NOTE]
|
||||||
================================
|
================================
|
||||||
The first `git clone` places the following in the
|
The `pull` command knows where to get updates from because of certain
|
||||||
`my-project/.git/remotes/origin` file, and that's why the previous step
|
configuration variables that were set by the first `git clone`
|
||||||
and the next step both work.
|
command; see `git repo-config -l` and the gitlink:git-repo-config[1] man
|
||||||
------------
|
page for details.
|
||||||
URL: foo.com:/pub/project.git/
|
|
||||||
Pull: refs/heads/master:refs/remotes/origin/master
|
|
||||||
------------
|
|
||||||
================================
|
================================
|
||||||
|
|
||||||
You can update the shared repository with your changes by first committing
|
You can update the shared repository with your changes by first committing
|
||||||
|
Loading…
Reference in New Issue
Block a user