Documentation/user-manual.txt: fix a few omissions of gitlink commands.
Signed-off-by: David Kastrup <dak@gnu.org>
David Kastrup committed
Aug 8, 2007 at 17:34 UTC
a115daff12d8d26975ff15a4278a212df2c8c70b
1 file changed
+8
-6
Documentation/user-manual.txt
+8
-6
@@ -1728,11 +1728,12 @@ taken from the message containing each patch.
1728
Public git repositories
1729
-----------------------
1730
1731
-Another way to submit changes to a project is to tell the maintainer of
1732
-that project to pull the changes from your repository using git-pull[1].
1733
-In the section "<<getting-updates-with-git-pull, Getting updates with
1734
-git pull>>" we described this as a way to get updates from the "main"
1735
-repository, but it works just as well in the other direction.
1731
+Another way to submit changes to a project is to tell the maintainer
1732
+of that project to pull the changes from your repository using
1733
+gitlink:git-pull[1]. In the section "<<getting-updates-with-git-pull,
1734
+Getting updates with git pull>>" we described this as a way to get
1735
+updates from the "main" repository, but it works just as well in the
1736
+other direction.
1737
1738
If you and the maintainer both have accounts on the same machine, then
1739
you can just pull changes from each other's repositories directly;
@@ -1989,7 +1990,8 @@ $ cd work
1990
Linus's tree will be stored in the remote branch named origin/master,
1991
and can be updated using gitlink:git-fetch[1]; you can track other
1992
public trees using gitlink:git-remote[1] to set up a "remote" and
1992
-git-fetch[1] to keep them up-to-date; see <<repositories-and-branches>>.
1993
+gitlink:git-fetch[1] to keep them up-to-date; see
1994
+<<repositories-and-branches>>.
1995
1996
Now create the branches in which you are going to work; these start out
1997
at the current tip of origin/master branch, and should be set up (using