2015-03-14 6:57 GMT+03:00 lilydjwg <[email protected]>: > On Fri, Mar 13, 2015 at 07:43:57AM -0700, Ben Fritz wrote: >> [...] >> >> Yes, that's mostly what I was referring to. While long-time git users may >> find it obvious that push --force is a stupid thing to do, new git users >> may not realize that. I sure would not have thought of that; I certainly >> would never have thought that it could destroy commits on the public >> repository. > > When I'm about to use an option called "--force", I will check the docs > to know exactly what will happen. If I don't understand that, I either > won't do it, or make a full backup before doing it. > > I guess git push should better remove the short option "-f". Pacman has > removed that already :-) > > PS: switching branches is slower for mercurial than git, at least with > CPython's source code.
Knowing what --force does cannot protect yourself from being stupid: check out my story few messages later. This was a bad mistake on my side, but git allows such bad mistakes. Mercurial does not: the worst thing you may do by pushing is creating a new head. If changeset evolution is supported on the remote side (it is still experimental) you could mark some changesets as obsolete on the remote, effectively making them disappear in new pulls, but this problem is limited to non-publishing repositories only. You also can’t mark changesets as obsolete without actually having them in your local repository (from where you can always restore them). BTW, it appears that I either mistaken what mq was intended for or they no longer consider changeset evolution *just* as mq replacement: new documentation talks about what I thought changeset evolution should be used for. > > > -- > Best regards, > lilydjwg > > -- > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
