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

Re: [RFC] Reverting "git push logic change"?

From
sean <seanlkml@sympatico.ca>
Date
Jan 22, 2006, 21:42 UTC
Message-ID
<BAYC1-PASMTP0532B701820FA4ADB3C640AE110@CEZ.ICE>
In-Reply-To
<7vu0bw9ch7.fsf@assigned-by-dhcp.cox.net>

On Sun, 22 Jan 2006 13:31:00 -0800 Junio C Hamano <junkio@cox.net> wrote:

Show 7 quoted lines
> +If you created your shared repository by cloning from somewhere
> +else, you may have the `origin` branch.  Your developers
> +typically do not use that branch; remove it.  Otherwise, that
> +would be pushed back by the `git push origin` because your
> +developers' repository would surely have `origin` branch to keep
> +track of the shared repository, and would be counted as "exist
> +on both ends".

What about just always excluding the origin branch from being implicitly pushed; even if it does exist in both repositories? In the rare cases where it is actually desired to be pushed, it can be done explicitly.

Sean
Previous: Junio C HamanoNext: Junio C Hamano
Message 10 of 13 in “"git push" logic changed?”
  1. Greg KHJan 20, 2006
  2. Junio C HamanoJan 21, 2006
  3. Greg KHJan 21, 2006
  4. Junio C HamanoJan 21, 2006
  5. Junio C HamanoJan 21, 2006
  6. [RFC] Reverting "git push logic change"?Junio C Hamano, Jan 21, 2006
  7. Daniel BarkalowJan 22, 2006
  8. Junio C HamanoJan 22, 2006
  9. Junio C HamanoJan 22, 2006
  10. seanJan 22, 2006
  11. Junio C HamanoJan 22, 2006
  12. Junio C HamanoJan 23, 2006
  13. Greg KHJan 24, 2006

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.