Get rid of a double pair of parentheses. The arbitrary SHA1 is a special case, so it can be postponed a bit. Also mention HEAD, which is possibly the most useful SHA1 in this situation. Mention that a SHA1 cannot be automatically matched to a <dst>. Add HEAD as an example of an arbitrary SHA1. Signed-off-by: Anders Melchiorsen <mail@xxxxxxxxxxxxxxxx> --- Documentation/git-push.txt | 12 +++++++++--- 1 files changed, 9 insertions(+), 3 deletions(-) diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 02c7dae..fb9fb97 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -38,9 +38,7 @@ OPTIONS by the source ref, followed by a colon `:`, followed by the destination ref. + -The <src> side represents the source branch (or arbitrary -"SHA1 expression", such as `master~4` (four parents before the -tip of `master` branch); see linkgit:git-rev-parse[1]) that you +The <src> side represents the source branch that you want to push. The <dst> side represents the destination location. + The local ref that matches <src> is used @@ -63,6 +61,10 @@ the local side, the remote side is updated if a head of the same name already exists on the remote side. This is the default operation mode if no explicit refspec is found (that is neither on the command line nor in any Push line of the corresponding remotes file---see below). ++ +The <src> can be an arbitrary "SHA1 expression", such as `HEAD` +or `master~4` (see linkgit:git-rev-parse[1]). In this case, a +<dst> location has to be named. --all:: Instead of naming each ref to push, specifies that all @@ -193,6 +195,10 @@ git push origin master:: with it. If `master` did not exist remotely, it would be created. +git push origin HEAD:master:: + Push the current head to the remote ref matching `master` in + the `origin` repository. + git push origin :experimental:: Find a ref that matches `experimental` in the `origin` repository (e.g. `refs/heads/experimental`), and delete it. -- 1.6.0.2.514.g23abd3 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
