{"thread":{"id":"9438","subject":"[PATCH] Documentation/user-manual.txt: fix a few omissions of gitlink commands.","startedAt":"2007-08-08T15:34:28Z","lastAt":"2007-08-08T15:34:28Z","messageCount":1,"participants":["David Kastrup"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"50197","messageId":"86hcnat4uk.fsf@lola.quinscape.zz","threadId":"9438","inReplyTo":null,"subject":"[PATCH] Documentation/user-manual.txt: fix a few omissions of gitlink commands.","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-08-08T15:34:28Z","receivedAt":"2007-08-08T15:34:28Z","isPatch":true,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"\nSigned-off-by: David Kastrup <dak@gnu.org>\n---\n Documentation/user-manual.txt |   20 +++++++++++---------\n 1 files changed, 11 insertions(+), 9 deletions(-)\n\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex f89952a..4c9d69b 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -1796,11 +1796,12 @@ taken from the message containing each patch.\n Public git repositories\n -----------------------\n \n-Another way to submit changes to a project is to tell the maintainer of\n-that project to pull the changes from your repository using git-pull[1].\n-In the section \"<<getting-updates-with-git-pull, Getting updates with\n-git pull>>\" we described this as a way to get updates from the \"main\"\n-repository, but it works just as well in the other direction.\n+Another way to submit changes to a project is to tell the maintainer\n+of that project to pull the changes from your repository using\n+gitlink:git-pull[1].  In the section \"<<getting-updates-with-git-pull,\n+Getting updates with git pull>>\" we described this as a way to get\n+updates from the \"main\" repository, but it works just as well in the\n+other direction.\n \n If you and the maintainer both have accounts on the same machine, then\n you can just pull changes from each other's repositories directly;\n@@ -2057,7 +2058,8 @@ $ cd work\n Linus's tree will be stored in the remote branch named origin/master,\n and can be updated using gitlink:git-fetch[1]; you can track other\n public trees using gitlink:git-remote[1] to set up a \"remote\" and\n-git-fetch[1] to keep them up-to-date; see <<repositories-and-branches>>.\n+gitlink:git-fetch[1] to keep them up-to-date; see\n+<<repositories-and-branches>>.\n \n Now create the branches in which you are going to work; these start out\n at the current tip of origin/master branch, and should be set up (using\n@@ -2512,9 +2514,9 @@ $ gitk origin..mywork &\n And browse through the list of patches in the mywork branch using gitk,\n applying them (possibly in a different order) to mywork-new using\n cherry-pick, and possibly modifying them as you go using commit --amend.\n-The git-gui[1] command may also help as it allows you to individually\n-select diff hunks for inclusion in the index (by right-clicking on the\n-diff hunk and choosing \"Stage Hunk for Commit\").\n+The gitlink:git-gui[1] command may also help as it allows you to\n+individually select diff hunks for inclusion in the index (by\n+right-clicking on the diff hunk and choosing \"Stage Hunk for Commit\").\n \n Another technique is to use git-format-patch to create a series of\n patches, then reset the state to before the patches:\n-- \n1.5.3.rc4.43.gaf14\n"}]}