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
Junio C Hamano <gitster@pobox.com>
Date
Mar 19, 2012, 21:43 UTC
Message-ID
<7v62e09sig.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4F6792DE.80208@pileofstuff.org>
Andrew Sayers <andrew-git@pileofstuff.org> writes:
Show 15 quoted lines
> On 18/03/12 18:50, Junio C Hamano wrote:
>> 
>> ... but in short, it is not a problem we can solve
>> (nor we should be solving), as long as we have a reasonable migration plan
>> and if the user is locked out of that migration plan---whoever is doing
>> the locking-out is taking responsibility for these users who are out of
>> our reach.
>
> I take the point that distros have their own support infrastructure, so
> perhaps this would be a better example:
>
> Many administrators in corporate environments will install git from
> source, because they don't trust RPM/need some feature in the latest
> version/are just that way inclined.  Having installed it, they tend to
> sit on that version for a few years ...

The same response applies. These administrators are taking responsibility for their users by making them out of our reach.

Show 7 quoted lines
> ... a
> slightly better solution:
>
> When a user upgrades to a mid- or post-change version of git, I think
> it's a good idea for them to be warned about the change of behaviour.
> But new users, and old users with new repositories, gain nothing from
> the little history lesson.

You are right for new users, but are wrong for old users who aren't aware of the switch-over, *and* are harmed by the switch-over.

Previous: Andrew SayersNext: demerphq
Message 9 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.