From 57b92a77a0aeff49e82cc0bfd14eac9313683766 Mon Sep 17 00:00:00 2001 From: Michael J Gruber Date: Tue, 27 Jan 2015 13:35:53 +0100 Subject: [PATCH] git-push.txt: document the behavior of --repo As per the code, the --repo option is equivalent to the argument to 'git push', but somehow it was documented as something that is more than that. [It exists for historical reasons, back from the time when options had to come before arguments.] Say so. [But not that.] Signed-off-by: Michael J Gruber Helped-by: Eric Sunshine Signed-off-by: Junio C Hamano --- Documentation/git-push.txt | 18 ++---------------- 1 file changed, 2 insertions(+), 16 deletions(-) diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 21cd455508..aea848a782 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -207,22 +207,8 @@ origin +master` to force a push to the `master` branch). See the `...` section above for details. --repo=:: - This option is only relevant if no argument is - passed in the invocation. In this case, 'git push' derives the - remote name from the current branch: If it tracks a remote - branch, then that remote repository is pushed to. Otherwise, - the name "origin" is used. For this latter case, this option - can be used to override the name "origin". In other words, - the difference between these two commands -+ --------------------------- -git push public #1 -git push --repo=public #2 --------------------------- -+ -is that #1 always pushes to "public" whereas #2 pushes to "public" -only if the current branch does not track a remote branch. This is -useful if you write an alias or script around 'git push'. + This option is equivalent to the argument. If both + are specified, the command-line argument takes precedence. -u:: --set-upstream::