more manual page updates following the introduction of 'got send'
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177
diff --git a/got/got.1 b/got/got.1
index d04a930..6cbbf9b 100644
--- a/got/got.1
+++ b/got/got.1
@@ -2532,7 +2532,9 @@ to be amended and perhaps committed again:
.Dl $ # now back out the previous backout :-)
.Dl $ got backout unified-buffer-cache
.Pp
-Fetch new upstream commits into the local repository's
+Fetch new changes on the remote repository's
+.Dq master
+branch, making them visible on the local repository's
.Dq origin/master
branch:
.Pp
@@ -2582,40 +2584,6 @@ branch:
.Dl $ got update -c master
.Dl $ got histedit
.Pp
-In order to merge changes committed to the
-.Dq unified-buffer-cache
-branch back into the
-.Dq master
-branch, the
-.Dq unified-buffer-cache
-branch must first be rebased onto the
-.Dq master
-branch:
-.Pp
-.Dl $ got update -b master
-.Dl $ got rebase unified-buffer-cache
-.Pp
-Changes on the
-.Dq unified-buffer-cache
-branch can now be made visible on the
-.Dq master
-branch with
-.Cm got integrate .
-Because the rebase operation switched the work tree to the
-.Dq unified-buffer-cache
-branch, the work tree must be switched back to the
-.Dq master
-branch before the
-.Dq unified-buffer-cache
-branch can be integrated into
-.Dq master :
-.Pp
-.Dl $ got update -b master
-.Dl $ got integrate unified-buffer-cache
-.Pp
-Additional steps may be necessary if local changes need to be pushed back
-to the remote repository, which currently requires
-.Cm git push .
Before working against existing branches in a repository cloned with
.Cm git clone --bare
instead of
@@ -2661,31 +2629,70 @@ namespace free for use by local branches checked out with
.Cm got checkout
and, if needed, created with
.Cm got branch .
-.Pp
Branches in the
-.Dq remotes/origin
+.Dq refs/remotes/origin
namespace can now be updated with incoming changes from the remote
repository with
.Cm got fetch
or
.Xr git-fetch 1
-without extra command line arguments:
-.Pp
-.Dl $ cd /var/git/repo
-.Dl $ git fetch
+without extra command line arguments.
+Newly fetched changes can be examined with
+.Cm got log .
.Pp
-To make changes fetched from the remote repository appear on the
+Display changes on the remote repository's version of the
.Dq master
-branch, the
-.Dq master
-branch must be rebased onto the
+branch, as of the last time
+.Cm got fetch
+was run:
+.Pp
+.Dl $ got log -c origin/master | less
+.Pp
+As shown here, most commands accept abbreviated reference names such as
.Dq origin/master
+instead of
+.Dq refs/remotes/origin/master .
+The latter is only needed in case of ambiguity.
+.Pp
+.Cm got rebase
+must be used to merge changes which are visible on the
+.Dq origin/master
+branch into the
+.Dq master
branch.
This will also merge local changes, if any, with the incoming changes:
.Pp
.Dl $ got update -b origin/master
.Dl $ got rebase master
.Pp
+In order to make changes committed to the
+.Dq unified-buffer-cache
+visible on the
+.Dq master
+branch, the
+.Dq unified-buffer-cache
+branch must first be rebased onto the
+.Dq master
+branch:
+.Pp
+.Dl $ got update -b master
+.Dl $ got rebase unified-buffer-cache
+.Pp
+Changes on the
+.Dq unified-buffer-cache
+branch can now be made visible on the
+.Dq master
+branch with
+.Cm got integrate .
+Because the rebase operation switched the work tree to the
+.Dq unified-buffer-cache
+branch the work tree must be switched back to the
+.Dq master
+branch first:
+.Pp
+.Dl $ got update -b master
+.Dl $ got integrate unified-buffer-cache
+.Pp
On the
.Dq master
branch, log messages for local changes can now be amended with
@@ -2695,13 +2702,25 @@ by other developers and any other important new information:
.Dl $ got update -c origin/master
.Dl $ got histedit -m
.Pp
-Local changes on the
+If the remote repository offers write access local changes on the
.Dq master
-branch can then be pushed to the remote
-repository with
-.Cm git push :
+branch can be sent to the remote repository with
+.Cm got send.
+Usually,
+.Cm got send
+can be run without further arguments.
+The arguments shown here match defaults, provided the work tree's
+current branch is the
+.Dq master
+branch:
.Pp
-.Dl $ cd /var/git/repo
+.Dl $ got send -b master origin
+.Pp
+If the remote repository requires the HTTPS protocol the
+.Xr git-push 1
+command must be used instead:
+.Pp
+.Dl $ cd /var/git/src.git
.Dl $ git push origin master
.Sh SEE ALSO
.Xr gotadmin 1 ,
@@ -2729,7 +2748,7 @@ Reading from remote repositories over HTTP or HTTPS protocols requires
and
.Xr git-fetch 1 .
.It
-Writing to remote repositories, over any protocol, requires
+Writing to remote repositories over HTTP or HTTPS protocols requires
.Xr git-push 1 .
.It
The creation of merge commits, i.e. commits with two or more parent commits,