From: Chris Johnsen Date: Sun, 15 Mar 2009 02:32:01 GMT Subject: [PATCH v2] git-push.txt: describe how to default to pushing only current branch Message-ID: <1237084321-14492-1-git-send-email-chris_johnsen@pobox.com> In-Reply-To: <7vd4cjc3da.fsf@gitster.siamese.dyndns.org> Signed-off-by: Chris Johnsen --- On 2009 Mar 14, at 14:26, Junio C Hamano wrote: > The new text looks reasonable. Sign-off? Oops, sorry for the omission. Here it is again with the S-o-B (or insert it by hand if you like). --- Documentation/git-push.txt | 26 ++++++++++++++++++++++++-- 1 files changed, 24 insertions(+), 2 deletions(-) diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 4e7e5a7..fd53c49 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -24,8 +24,8 @@ every time you push into it, by setting up 'hooks' there. See documentation for linkgit:git-receive-pack[1]. -OPTIONS -------- +OPTIONS[[OPTIONS]] +------------------ :: The "remote" repository that is destination of a push operation. This parameter can be either a URL @@ -187,6 +187,28 @@ reason:: Examples -------- +git push:: + Works like `git push `, where is the + current branch's remote (or `origin`, if no remote is + configured for the current branch). + +git push origin:: + Without additional configuration, works like + `git push origin :`. ++ +The default behavior of this command when no is given can be +configured by setting the `push` option of the remote. ++ +For example, to default to pushing only the current branch to `origin` +use `git config remote.origin.push HEAD`. Any valid (like +the ones in the examples below) can be configured as the default for +`git push origin`. + +git push origin ::: + Push "matching" branches to `origin`. See + in the <> section above for a + description of "matching" branches. + git push origin master:: Find a ref that matches `master` in the source repository (most likely, it would find `refs/heads/master`), and update -- 1.6.2