News for hackers. Stuff that matters.
Re:Mercurial vs Git; it’s all in the branches by BerislavLopac on Saturday January 07, 2012 @01:25PM (#3437644)
To me, it's obvious that the author has entered the comparison with a very strong git bias, so it is only naturally that git won eventually.

He is right on one thing: the differences are mostly subtle, the most glaring one being whether history is allowed to be rewritten or not. In the end it all comes down to personal preferences, and my personal experience is strongly in favor of hg.

Re:Mercurial vs Git; it’s all in the branches by parfe on Saturday January 07, 2012 @01:26PM (#3437647)
>To me, it's obvious that the author has entered the comparison with a very strong git bias, so it is only naturally that git won eventually.

Was it obvious because he specifically notes it in the intro to the article?

Note: I’m a long-time advocate of Git, and a contributor to the project, so I am biased (but I hope my conclusions are not).

Re:Mercurial vs Git; it’s all in the branches by eipipuz on Saturday January 07, 2012 @01:48PM (#3437711)
That's not obvious. He clearly says he hopes his conclusions would go beyond his bias.

He failed to do so, but we couldn't know that without reading the article.

Re:Mercurial vs Git; it’s all in the branches by eslaught on Saturday January 07, 2012 @03:54PM (#3438052)
The author seems to contradict himself in a comment[1]: My objective is to show why Git is superior. (Thanks to [2] for noticing.)

[1]: http://felipec.wordpress.com/2011/01/16/mercurial-vs-git-its...

[2]: http://news.ycombinator.com/item?id=3437677

Re:Mercurial vs Git; it’s all in the branches by felipec on Sunday January 08, 2012 @12:43PM (#3440028)
It's not a contradiction. Note the word why. If in the analysis it turns out I fail to show that git is indeed superior, I would have to agree mercurial is superior, or they are equal.

That was not the case.

Re:Mercurial vs Git; it’s all in the branches by BerislavLopac on Saturday January 07, 2012 @01:52PM (#3437728)
LOL no, I missed that one. But the sibling is correct, the author failed.
Re:Mercurial vs Git; it’s all in the branches by felipec on Sunday January 08, 2012 @12:48PM (#3440039)
Saying "the author failed" is easy. Presenting a case that demonstrates so is not.

What I said is that they are basically the same, except for the handling of branches, not history rewriting as you suggest.

I assume you agree that they are basically the same, now, if you disagree that the handling of branches is superior in git, feel free to add a comment in my blog, but after 160 comments, nobody has managed to contradict that conclusion.

So no, nobody has managed to prove where exactly is the bias. It is possible that git is superior, and that's what the evidence suggests.

Re:Mercurial vs Git; it’s all in the branches by masklinn on Saturday January 07, 2012 @01:49PM (#3437719)
> the most glaring one being whether history is allowed to be rewritten or not.

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.

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?
Re:Mercurial vs Git; it’s all in the branches by stevecooperorg on Saturday January 07, 2012 @06:57PM (#3438429)
Yeah, this wasn't a straight comparison, but an act of apologetics.