# [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master 4 messages from 2007-09-18 to 2007-09-19. Participants: Jari Aalto, Johannes Schindelin, Junio C Hamano. Thread: https://gitlist.dev/t/9920 ## Jari Aalto, 2007-09-18 09:59 Subject: [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master Message-ID: URL: https://gitlist.dev/e/wsuomgyu.fsf%40blue.sea.net ``` Signed-off-by: Jari Aalto --- Documentation/git-push.txt | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 7b8e075..71ac450 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -105,7 +105,9 @@ git push origin master:: Find a ref that matches `master` in the source repository (most likely, it would find `refs/heads/master`), and update the same ref (e.g. `refs/heads/master`) in `origin` repository - with it. + with it. The following would be exactly same command: + + git push origin master:refs/heads/master git push origin :experimental:: Find a ref that matches `experimental` in the `origin` repository -- 1.5.3 -- Welcome to FOSS revolution: we fix and modify until it shines ``` ## Johannes Schindelin, 2007-09-18 12:01 Subject: Re: [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master Message-ID: URL: https://gitlist.dev/e/Pine.LNX.4.64.0709181300380.28586%40racer.site In-Reply-To: ``` Hi, On Tue, 18 Sep 2007, Jari Aalto wrote: > [no meaningful commit message] Your patch is wrong. Try "git push origin ". Works like a charm, without starting a new branch. Ciao, Dscho ``` ## Junio C Hamano, 2007-09-18 20:54 Subject: Re: [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master Message-ID: <7vfy1bvgn1.fsf@gitster.siamese.dyndns.org> URL: https://gitlist.dev/e/7vfy1bvgn1.fsf%40gitster.siamese.dyndns.org In-Reply-To: ``` Jari Aalto writes: > Signed-off-by: Jari Aalto > --- > Documentation/git-push.txt | 4 +++- > 1 files changed, 3 insertions(+), 1 deletions(-) > > diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt > index 7b8e075..71ac450 100644 > --- a/Documentation/git-push.txt > +++ b/Documentation/git-push.txt > @@ -105,7 +105,9 @@ git push origin master:: > Find a ref that matches `master` in the source repository > (most likely, it would find `refs/heads/master`), and update > the same ref (e.g. `refs/heads/master`) in `origin` repository > - with it. > + with it. The following would be exactly same command: > + > + git push origin master:refs/heads/master They _might_ be exactly the same. The reason people often explicitly write $ git push $URL refs/heads/master:refs/heads/master in their insns for newbies is because this form would not be affected by the random factors at $URL repository (or your repository) and will consistently get the same result. $ git push $URL foo may push branch head 'foo' or tag 'foo' depending on which one you have locally. Having both is not encouraged, but spelling the insn out explicitly as refs/heads/foo makes it clear the command is talking about the branch even when there is a tag with the same name. ``` ## Jari Aalto, 2007-09-19 10:37 Subject: Re: [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master Message-ID: URL: https://gitlist.dev/e/bqbzj5ze.fsf%40blue.sea.net In-Reply-To: <7vfy1bvgn1.fsf@gitster.siamese.dyndns.org> ``` * Tue 2007-09-18 Junio C Hamano * Message-Id: 7vfy1bvgn1.fsf AT gitster.siamese.dyndns.org >> Find a ref that matches `master` in the source repository >> (most likely, it would find `refs/heads/master`), and update >> the same ref (e.g. `refs/heads/master`) in `origin` repository >> - with it. >> + with it. The following would be exactly same command: >> + >> + git push origin master:refs/heads/master > > They _might_ be exactly the same. > > The reason people often explicitly write > > $ git push $URL refs/heads/master:refs/heads/master > > in their insns for newbies is because this form would not be > affected by the random factors at $URL repository (or your > repository) and will consistently get the same result. > > $ git push $URL foo > > may push branch head 'foo' or tag 'foo' depending on which one > you have locally. Having both is not encouraged, but spelling > the insn out explicitly as refs/heads/foo makes it clear the > command is talking about the branch even when there is a tag > with the same name. Thank you, kindly broaden the current documentation to include this explanation. Jari -- Welcome to FOSS revolution: we fix and modify until it shines ```