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

Re: Please discuss: what "git push" should do when you do not say what to push?

From
ASAndrew Sayers <andrew-git@pileofstuff.org>
Date
Mar 20, 2012, 23:41 UTC
Message-ID
<4F6915A8.9040009@pileofstuff.org>
In-Reply-To
<7vhaxi50q8.fsf@alter.siamese.dyndns.org>
On 20/03/12 23:09, Junio C Hamano wrote:
Show 20 quoted lines
> Andrew Sayers <andrew-git@pileofstuff.org> writes:
> 
>> I assume the reason for removing the warning altogether is that some day
>> the signal:noise ratio will just get too bad.
> 
> The reasoning is a lot simpler than that.
> 
> If the end game is not remove the warning, then we would be switching to a
> new default that is "give loud warning until the user configures her own
> default, but push upstream/current anyway" mode.  We do not want such a
> stupid mode as the default---we want the default to be either upstream or
> current at the end, when nobody remembers what the ancient default was.
> 
> The "warn loud but do it anyway" is a very good interim step during the
> migration, but is never a good default.  If we are going to stop there,
> "give loud warning until the user chooses and configures the default, and
> push nothing" mode would be a LOT safer and saner default, as it would
> really force people to configure the default.  Obviously we do not want to
> go there, so...
>

It sounds like we're disagreeing, but I can't tell what about. I agree that "warn loud but do it anyway" is a bad default in the long term. I propose implementing the behaviour you want by adding a push.default setting to the .git/config file for all new repositories, so that users with a longer-than-expected short term still get the warning. That should warn 99% of the people who need it without bothering anyone that doesn't. What am I missing?

	- Andrew
Previous: Junio C HamanoNext: Junio C Hamano
Message 17 of 43 in “Please discuss: what "git push" should do when you do not say what to push?”
  1. Junio C HamanoMar 17, 2012
  2. Junio C HamanoMar 17, 2012
  3. Andrew SayersMar 17, 2012
  4. Junio C HamanoMar 18, 2012
  5. Ævar Arnfjörð BjarmasonMar 18, 2012
  6. Junio C HamanoMar 19, 2012
  7. Sebastien DoucheMar 19, 2012
  8. Andrew SayersMar 19, 2012
  9. Junio C HamanoMar 19, 2012
  10. demerphqMar 19, 2012
  11. Junio C HamanoMar 19, 2012
  12. Andreas EricssonMar 20, 2012
  13. Andrew SayersMar 19, 2012
  14. Junio C HamanoMar 19, 2012
  15. Andrew SayersMar 20, 2012
  16. Junio C HamanoMar 20, 2012
  17. Andrew SayersMar 20, 2012
  18. Junio C HamanoMar 21, 2012
  19. Martin LanghoffMar 20, 2012
  20. Junio C HamanoMar 20, 2012
  21. Martin LanghoffMar 20, 2012
  22. Jakub NarebskiMar 20, 2012
  23. Summary of discussion on "git push" default changeJunio C Hamano, Mar 21, 2012
  24. Matthieu MoyMar 21, 2012
  25. Joey HessMar 17, 2012
  26. Junio C HamanoMar 19, 2012
  27. fREW SchmidtMar 17, 2012
  28. H. Peter AnvinMar 18, 2012
  29. Marcus D. HanwellMar 18, 2012
  30. Sebastian SchuberthMar 18, 2012
  31. Peter KreftingMar 19, 2012
  32. Letting remote repositories override local configurationJonathan Nieder, Mar 19, 2012
  33. Peter KreftingMar 19, 2012
  34. Kevin BallardMar 19, 2012
  35. Antony MaleMar 20, 2012
  36. Jakub NarebskiMar 20, 2012
  37. Antony MaleMar 20, 2012
  38. Nathan GrayMar 20, 2012
  39. Ben TebulinMar 20, 2012
  40. Ben TebulinMar 20, 2012
  41. Ben TebulinMar 20, 2012
  42. Ben TebulinMar 20, 2012
  43. Filipe FernandesMar 20, 2012

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.