summaryrefslogtreecommitdiff
path: root/Documentation/user-manual.txt
diff options
context:
space:
mode:
authorDavid Kastrup <dak@gnu.org>2007-08-08 15:34:28 (GMT)
committerJ. Bruce Fields <bfields@citi.umich.edu>2007-08-26 14:35:17 (GMT)
commita115daff12d8d26975ff15a4278a212df2c8c70b (patch)
treed93c5b1f61c46cdc4d19cf9fc01ffcf2da3469ac /Documentation/user-manual.txt
parentd5821de2e29a3a207a2c5188f73b7d1f6d52fc34 (diff)
downloadgit-a115daff12d8d26975ff15a4278a212df2c8c70b.zip
git-a115daff12d8d26975ff15a4278a212df2c8c70b.tar.gz
git-a115daff12d8d26975ff15a4278a212df2c8c70b.tar.bz2
Documentation/user-manual.txt: fix a few omissions of gitlink commands.
Signed-off-by: David Kastrup <dak@gnu.org>
Diffstat (limited to 'Documentation/user-manual.txt')
-rw-r--r--Documentation/user-manual.txt14
1 files changed, 8 insertions, 6 deletions
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 1c3f0e6..2e8c050 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -1728,11 +1728,12 @@ taken from the message containing each patch.
Public git repositories
-----------------------
-Another way to submit changes to a project is to tell the maintainer of
-that project to pull the changes from your repository using git-pull[1].
-In the section "<<getting-updates-with-git-pull, Getting updates with
-git pull>>" we described this as a way to get updates from the "main"
-repository, but it works just as well in the other direction.
+Another way to submit changes to a project is to tell the maintainer
+of that project to pull the changes from your repository using
+gitlink:git-pull[1]. In the section "<<getting-updates-with-git-pull,
+Getting updates with git pull>>" we described this as a way to get
+updates from the "main" repository, but it works just as well in the
+other direction.
If you and the maintainer both have accounts on the same machine, then
you can just pull changes from each other's repositories directly;
@@ -1989,7 +1990,8 @@ $ cd work
Linus's tree will be stored in the remote branch named origin/master,
and can be updated using gitlink:git-fetch[1]; you can track other
public trees using gitlink:git-remote[1] to set up a "remote" and
-git-fetch[1] to keep them up-to-date; see <<repositories-and-branches>>.
+gitlink:git-fetch[1] to keep them up-to-date; see
+<<repositories-and-branches>>.
Now create the branches in which you are going to work; these start out
at the current tip of origin/master branch, and should be set up (using