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

Re: git push

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 25, 2009, 09:26 UTC
Message-ID
<7viqmy7tqk.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20090225090230.GA15919@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> But I don't buy this at all. It is totally dependent on workflow and how
> you use branches.

Of course. "Encouraging a behaviour" means just that. A better workflow and a better use of branches.

> When you think about "is my current branch ready to push?" there is no
> reason for you to think of that other long-running branch that you
> haven't seen for days.
Sorry, I have to disagree with that.

We are talking about people to whom the "push matching refs" is a problem, and that means they are using a branch with the same name with other people (either from a shared central repository or his own publishing branch) to house long-running, intermediate, uncooked state.

Why aren't you forking off your own topic branch from such a branch that is either shared (or for publishing)? For the purpose of this discussion, shared branch is the same as your own publishing branch -- that's where you put things that are *ready* to be seen by other people.

The one you haven't seen for days, if it is not shared, won't bother you nor your "matching push", because you wouldn't have merged your uncooked changes from your own topic branch to that shared branch yet.

Previous: Jeff KingNext: Jeff King
Message 7 of 17 in “git push”
  1. John TapsellFeb 25, 2009
  2. Jeff KingFeb 25, 2009
  3. Junio C HamanoFeb 25, 2009
  4. John TapsellFeb 25, 2009
  5. Junio C HamanoFeb 25, 2009
  6. Jeff KingFeb 25, 2009
  7. Junio C HamanoFeb 25, 2009
  8. Jeff KingFeb 25, 2009
  9. John TapsellFeb 25, 2009
  10. Junio C HamanoFeb 25, 2009
  11. John TapsellFeb 25, 2009
  12. Jay SoffianFeb 25, 2009
  13. Junio C HamanoFeb 25, 2009
  14. Finn Arne GangstadFeb 25, 2009
  15. Andreas EricssonMar 5, 2009
  16. John TapsellMar 5, 2009
  17. Finn Arne GangstadMar 5, 2009

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.