News for hackers. Stuff that matters.
Re:A Git catastrophe cleaned up by justinlaster on Wednesday December 21, 2016 @01:32PM (#13231429)
> If two branches have parent commits in common, it technically belongs to both branches.

It belongs to both branches as well in Mercurial, it just hides that information from you. An astoundingly bad idea, no? I'm not sure how mercurial hiding information from you is a "feature" in any sense of the word.

Re:A Git catastrophe cleaned up by binarycrusader on Wednesday December 21, 2016 @02:44PM (#13232023)
Hiding or encapsulating information is arguably part of the very nature of an abstraction; the CLIs provided by git and Mercurial could be considered an abstraction of the implementation details of the respective technologies.

As such, I fully expect each tool to hide some amount of information so that I don't have to think about the details.

Re:A Git catastrophe cleaned up by justinlaster on Wednesday December 21, 2016 @03:34PM (#13232387)
There's no easy quick way to represent the actual state of the commit. It's far easier in git because it's the only way to do it. Furthermore, then information being "encapsulated" can actually become stale or misleading in Mercurial.