diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2008-05-26 01:16:14 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2008-05-26 01:16:14 +0000 |
| commit | dfccbb0719b88f4df05bf718c6008166dbadea44 (patch) | |
| tree | ddd5483c51044cab7a070039655f0b4074b1dfe6 /user-manual.txt | |
| parent | b713ff1cbf5b9979edaf2b85bfc568fbc37ec0d7 (diff) | |
| download | git-htmldocs-dfccbb0719b88f4df05bf718c6008166dbadea44.tar.gz | |
Autogenerated HTML docs for v1.5.6-rc0
Diffstat (limited to 'user-manual.txt')
| -rw-r--r-- | user-manual.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/user-manual.txt b/user-manual.txt index e2db85015..fd8cdb625 100644 --- a/user-manual.txt +++ b/user-manual.txt @@ -1993,7 +1993,7 @@ the right to push to the same repository. In that case, the correct solution is to retry the push after first updating your work by either a pull or a fetch followed by a rebase; see the <<setting-up-a-shared-repository,next section>> and -link:cvs-migration.html[git for CVS users] for more. +linkgit:gitcvs-migration[7][git for CVS users] for more. [[setting-up-a-shared-repository]] Setting up a shared repository @@ -2002,7 +2002,7 @@ Setting up a shared repository Another way to collaborate is by using a model similar to that commonly used in CVS, where several developers with special rights all push to and pull from a single shared repository. See -link:cvs-migration.html[git for CVS users] for instructions on how to +linkgit:gitcvs-migration[7][git for CVS users] for instructions on how to set this up. However, while there is nothing wrong with git's support for shared |