3 ms·
People complain about missing abstractions, not leaky ones. Mercurial has leaky abstractions imho. A Mercurial changeset ("commit" in git terminology) has a bra
by qznc 10y ago
People complain about missing abstractions, not leaky ones. Mercurial has leaky abstractions imho. A Mercurial changeset ("commit" in git terminology) has a branch property. In git a commit does not belong to a certain branch. With both SCMs, most changesets/commits are on multiple branches, thus I consider the Mercurial abstraction leaky.
Mercurial people seem to like this, but it just doesn't fit my mental model.
- Siecje 10y agoI think you are talking about named branches in Mercurial. You can use Mercurial without named branches and use bookmarks instead.
- marcinkuzminski 10y agoExactly, there is the flexibility. IF you need to track source of commits together with the permanent branch info you use Mercurial branches, if you want a "symlink branches" in GIT style, bookmarks are the way to go. It works nice with Pull requests when you can move branch pointer after rebase or updates of commits.