3 ms·

So, is there anyone actually against this change?

• bostonvaulter2 15y ago
  Not on this hacker news page.
  • cookiecaper 15y ago
    Nor on LWN apparently. This has got to be the least controversial setting change in a good long time. It seems everyone just worked around this crappy default by establishing usage habits like always defining branch and remote. I know I've set my git push to current a couple of times but most of the time I just end up deleting the branch if something that wasn't intended for public consumption gets pushed up.
• nknight 15y ago
  There seems to be a small minority on the git mailing list who are split between questioning the workflow of anyone who needs this, and the obligatory and inane "it's documented, it's not a problem!" attitude
• JoshTriplett 15y ago
  Some debate exists over the correct default to switch to ("current" or "upstream"), but nobody seems to argue for today's behavior ("matching").