Re:Mercurial vs Git; it’s all in the branches
by BerislavLopac on Saturday January 07, 2012 @01:58PM
(#3437751)
OK, "supposed" might be a better choice than "allowed"; but that's splitting hairs.
Re:Mercurial vs Git; it’s all in the branches
by masklinn on Saturday January 07, 2012 @02:06PM
(#3437769)
No, "supposed" is almost as incorrect, mq is there in the standard distribution and most of its job is history rewriting (the mere act of popping a patch effectively rewrites history). `rebase`'s sole job is rewriting history.
> but that's splitting hairs.
Not being completely and utterly wrong is "splitting hairs"?
Furthermore, it makes very little sense to criticize a tool with no basis in the tool's capabilities themselves but based merely on its community's suggestions, do you also criticize Python because its community recommends underscore_separated method names and you prefer camelCase? I'm not saying the community is not important, but mercurial itself, as a tool, has absolutely no hangup on history rewriting.
Re:Mercurial vs Git; it’s all in the branches
by BerislavLopac on Saturday January 07, 2012 @02:57PM
(#3437915)
I'm sorry? Which tool was I criticizing exactly?
That's not even true, history is allowed to be rewritten in mercurial (mercurial-bundled extensions `rebase`, and `mq` as well as the standard `rollback` command do — or can be used to do — exactly that, and so do third-party extensions such as `histedit`), there's little difference on that point. The difference is the tendency to push for history-rewriting.