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

Re: git push origin error (1.6.3 new default functionality)

From
Johannes Sixt <j.sixt@viscovery.net>
Date
May 13, 2009, 08:44 UTC
Message-ID
<4A0A8871.6080107@viscovery.net>
In-Reply-To
<20090513083203.GA25058@sigill.intra.peff.net>
Context: This is about the warning that a plain "git push" produces if no
push refspec are configured. The default behavior is to push matching
branches.
Jeff King schrieb:
Show 6 quoted lines
> Or are you proposing to still change the default behavior, but drop the
> warning whose aim is to inform people about the impending change? In
> that case, I think you should address the concerns that arose from
> previous changes in default behavior (and which this warning is meant to
> address), and propose an alternate plan for making the transition more
> smooth.

Unfortunately, the case with this warning is not that "simple" because it is not about a planned change of the default behavior, but about a default behavior that may be unexpected for newbies (see the release notes of 1.6.3). I *can* understand that Caleb is upset by the warning, since he's comfortable with the (current and future) default behavior. But I don't know what to do in cases like these.

-- Hannes
Previous: Jeff KingNext: Jeff King
Message 5 of 14 in “git push origin error (1.6.3 new default functionality)”
  1. Caleb CushingMay 12, 2009
  2. Michael J GruberMay 12, 2009
  3. Caleb CushingMay 13, 2009
  4. Jeff KingMay 13, 2009
  5. Johannes SixtMay 13, 2009
  6. Jeff KingMay 13, 2009
  7. Michael J GruberMay 13, 2009
  8. Jeff KingMay 14, 2009
  9. Michael J GruberMay 14, 2009
  10. Junio C HamanoMay 13, 2009
  11. Caleb CushingMay 14, 2009
  12. Junio C HamanoMay 14, 2009
  13. Junio C HamanoMay 14, 2009
  14. Finn Arne GangstadMay 14, 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.