git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git push origin BRANCHNAME question

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 25, 2016, 17:50 UTC
Message-ID
<xmqqr39cn3fk.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<6c4fbb7d-6f67-b454-2b4b-9f5fbeffae9b@greenberg.org>
Ed Greenberg <edg@greenberg.org> writes:
Show 9 quoted lines
> I think I understand this from the git-push man page, but I want to
> make sure:
>
> I have two branches, master and develop.
>
> If I am (accidentally) sitting on master, and issue 'git push origin
> develop', does this properly push develop to remote develop, or does
> it push master to remote develop (which seems to be bad, in the most
> common use case.)  ?
You can find it out yourself quite easily, I would think.

$ git init src $ git init dst $ cd src $ git commit --allow-empty -m initial $ git checkout -b develop $ git commit --allow-empty -m second

$ git checkout master
$ git push ../dst develop
Counting objects: 3, done.
Delta compression using up to 6 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 226 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 0 (delta 0)
To ../dst
 * [new branch]      develop -> develop
Previous: Ed GreenbergNext: Jeff King
Message 2 of 3 in “git push origin BRANCHNAME question”
  1. Ed GreenbergAug 25, 2016
  2. Junio C HamanoAug 25, 2016
  3. Jeff KingAug 25, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.