{"thread":{"id":"9920","subject":"[PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master","startedAt":"2007-09-18T09:59:53Z","lastAt":"2007-09-19T10:37:41Z","messageCount":4,"participants":["Jari Aalto","Johannes Schindelin","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"53436","messageId":"wsuomgyu.fsf@blue.sea.net","threadId":"9920","inReplyTo":null,"subject":"[PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master","fromName":"Jari Aalto","fromEmail":"jari.aalto@cante.net","sentAt":"2007-09-18T09:59:53Z","receivedAt":"2007-09-18T09:59:53Z","isPatch":true,"sender":{"key":"jari.aalto@cante.net","avatar":"https://avatars.githubusercontent.com/u/34601?v=4"},"body":"Signed-off-by: Jari Aalto <jari.aalto AT cante.net>\n---\n Documentation/git-push.txt |    4 +++-\n 1 files changed, 3 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex 7b8e075..71ac450 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -105,7 +105,9 @@ git push origin master::\n \tFind a ref that matches `master` in the source repository\n \t(most likely, it would find `refs/heads/master`), and update\n \tthe same ref (e.g. `refs/heads/master`) in `origin` repository\n-\twith it.\n+\twith it. The following would be exactly same command:\n+\n+\tgit push origin master:refs/heads/master\n \n git push origin :experimental::\n \tFind a ref that matches `experimental` in the `origin` repository\n-- \n1.5.3\n\n\n-- \nWelcome to FOSS revolution: we fix and modify until it shines\n"},{"id":"53458","messageId":"Pine.LNX.4.64.0709181300380.28586@racer.site","threadId":"9920","inReplyTo":"wsuomgyu.fsf@blue.sea.net","subject":"Re: [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-09-18T12:01:32Z","receivedAt":"2007-09-18T12:01:32Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Tue, 18 Sep 2007, Jari Aalto wrote:\n\n> [no meaningful commit message]\n\nYour patch is wrong.  Try \"git push origin <some-tag>\".  Works like a \ncharm, without starting a new branch.\n\nCiao,\nDscho\n"},{"id":"53503","messageId":"7vfy1bvgn1.fsf@gitster.siamese.dyndns.org","threadId":"9920","inReplyTo":"wsuomgyu.fsf@blue.sea.net","subject":"Re: [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-09-18T20:54:26Z","receivedAt":"2007-09-18T20:54:26Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jari Aalto <jari.aalto@cante.net> writes:\n\n> Signed-off-by: Jari Aalto <jari.aalto AT cante.net>\n> ---\n>  Documentation/git-push.txt |    4 +++-\n>  1 files changed, 3 insertions(+), 1 deletions(-)\n>\n> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\n> index 7b8e075..71ac450 100644\n> --- a/Documentation/git-push.txt\n> +++ b/Documentation/git-push.txt\n> @@ -105,7 +105,9 @@ git push origin master::\n>  \tFind a ref that matches `master` in the source repository\n>  \t(most likely, it would find `refs/heads/master`), and update\n>  \tthe same ref (e.g. `refs/heads/master`) in `origin` repository\n> -\twith it.\n> +\twith it. The following would be exactly same command:\n> +\n> +\tgit push origin master:refs/heads/master\n\nThey _might_ be exactly the same.\n\nThe reason people often explicitly write\n\n\t$ git push $URL refs/heads/master:refs/heads/master\n\nin their insns for newbies is because this form would not be\naffected by the random factors at $URL repository (or your\nrepository) and will consistently get the same result.\n\n\t$ git push $URL foo\n\nmay push branch head 'foo' or tag 'foo' depending on which one\nyou have locally.  Having both is not encouraged, but spelling\nthe insn out explicitly as refs/heads/foo makes it clear the\ncommand is talking about the branch even when there is a tag\nwith the same name.\n"},{"id":"53571","messageId":"bqbzj5ze.fsf@blue.sea.net","threadId":"9920","inReplyTo":"7vfy1bvgn1.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master","fromName":"Jari Aalto","fromEmail":"jari.aalto@cante.net","sentAt":"2007-09-19T10:37:41Z","receivedAt":"2007-09-19T10:37:41Z","isPatch":true,"sender":{"key":"jari.aalto@cante.net","avatar":"https://avatars.githubusercontent.com/u/34601?v=4"},"body":"* Tue 2007-09-18 Junio C Hamano <gitster AT pobox.com>\n* Message-Id: 7vfy1bvgn1.fsf AT gitster.siamese.dyndns.org\n>>  \tFind a ref that matches `master` in the source repository\n>>  \t(most likely, it would find `refs/heads/master`), and update\n>>  \tthe same ref (e.g. `refs/heads/master`) in `origin` repository\n>> -\twith it.\n>> +\twith it. The following would be exactly same command:\n>> +\n>> +\tgit push origin master:refs/heads/master\n>\n> They _might_ be exactly the same.\n>\n> The reason people often explicitly write\n>\n> \t$ git push $URL refs/heads/master:refs/heads/master\n>\n> in their insns for newbies is because this form would not be\n> affected by the random factors at $URL repository (or your\n> repository) and will consistently get the same result.\n>\n> \t$ git push $URL foo\n>\n> may push branch head 'foo' or tag 'foo' depending on which one\n> you have locally.  Having both is not encouraged, but spelling\n> the insn out explicitly as refs/heads/foo makes it clear the\n> command is talking about the branch even when there is a tag\n> with the same name.\n\nThank you, kindly broaden the current documentation to include this\nexplanation.\n\nJari\n\n-- \nWelcome to FOSS revolution: we fix and modify until it shines\n"}]}