From a115daff12d8d26975ff15a4278a212df2c8c70b Mon Sep 17 00:00:00 2001 From: David Kastrup Date: Wed, 8 Aug 2007 17:34:28 +0200 Subject: [PATCH] Documentation/user-manual.txt: fix a few omissions of gitlink commands. Signed-off-by: David Kastrup --- Documentation/user-manual.txt | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 1c3f0e65f..2e8c050bb 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 "<>" 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 "<>" 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 <>. +gitlink:git-fetch[1] to keep them up-to-date; see +<>. 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 -- 2.26.2