* [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master
@ 2007-09-18 9:59 Jari Aalto
2007-09-18 12:01 ` Johannes Schindelin
2007-09-18 20:54 ` Junio C Hamano
0 siblings, 2 replies; 4+ messages in thread
From: Jari Aalto @ 2007-09-18 9:59 UTC (permalink / raw)
To: git
Signed-off-by: Jari Aalto <jari.aalto AT cante.net>
---
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
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master
2007-09-18 9:59 [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master Jari Aalto
@ 2007-09-18 12:01 ` Johannes Schindelin
2007-09-18 20:54 ` Junio C Hamano
1 sibling, 0 replies; 4+ messages in thread
From: Johannes Schindelin @ 2007-09-18 12:01 UTC (permalink / raw)
To: Jari Aalto; +Cc: git
Hi,
On Tue, 18 Sep 2007, Jari Aalto wrote:
> [no meaningful commit message]
Your patch is wrong. Try "git push origin <some-tag>". Works like a
charm, without starting a new branch.
Ciao,
Dscho
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master
2007-09-18 9:59 [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master Jari Aalto
2007-09-18 12:01 ` Johannes Schindelin
@ 2007-09-18 20:54 ` Junio C Hamano
2007-09-19 10:37 ` Jari Aalto
1 sibling, 1 reply; 4+ messages in thread
From: Junio C Hamano @ 2007-09-18 20:54 UTC (permalink / raw)
To: Jari Aalto; +Cc: git
Jari Aalto <jari.aalto@cante.net> writes:
> Signed-off-by: Jari Aalto <jari.aalto AT cante.net>
> ---
> 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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master
2007-09-18 20:54 ` Junio C Hamano
@ 2007-09-19 10:37 ` Jari Aalto
0 siblings, 0 replies; 4+ messages in thread
From: Jari Aalto @ 2007-09-19 10:37 UTC (permalink / raw)
To: git
* Tue 2007-09-18 Junio C Hamano <gitster AT pobox.com>
* 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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-09-19 10:38 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-09-18 9:59 [PATCH] Mention that 'push .. master' is in explicit form master:refs/heads/master Jari Aalto
2007-09-18 12:01 ` Johannes Schindelin
2007-09-18 20:54 ` Junio C Hamano
2007-09-19 10:37 ` Jari Aalto
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).