From 4e560158c6de154fafab9fc3f6028d9edcc53e6b Mon Sep 17 00:00:00 2001 From: "Shawn O. Pearce" Date: Thu, 6 Sep 2007 00:44:08 -0400 Subject: [PATCH] Include a git-push example for creating a remote branch Many users get confused when `git push origin master:foo` works when foo already exists on the remote repository but are confused when foo doesn't exist as a branch and this form does not create the branch foo. This new example highlights the trick of including refs/heads/ in front of the desired branch name to create a branch. Signed-off-by: Shawn O. Pearce Signed-off-by: Junio C Hamano --- Documentation/git-push.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 0dd9caf867..7b8e075c42 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -117,6 +117,12 @@ git push origin master:satellite/master:: the ref that matches `satellite/master` (most likely, it would be `refs/remotes/satellite/master`) in `origin` repository with it. +git push origin master:refs/heads/experimental:: + Create the branch `experimental` in the `origin` repository + by copying the current `master` branch. This form is usually + needed to create a new branch in the remote repository as + there is no `experimental` branch to match. + Author ------ Written by Junio C Hamano , later rewritten in C