4 ms·
> When you are done with the ‘quick-fix’ branch, you can just remove it, and nobody has to know it existed Well, I actually want to know about branches. If som
by k_bx 14y ago
> When you are done with the ‘quick-fix’ branch, you can just remove it, and nobody has to know it existed
Well, I actually want to know about branches. If someone finishes work on some branch, he'll just close it after merge. Also, "hg branch" command will sort out non-merged branches from merged. This is so handy.
One thing that bugs me in git branches is that only gitk shows branches (in git's strange way, when topmost commit has tons of branches assigned to it), while in mercurial nearly all clients show branch info beside commit, since it's a core feature and it's stored in commit.
I am now working with git for >6 month (after >1 year work with hg) and every time I feel some mess with branches/merges it feels very uncomfortable.
So, for non-huge projects, hg branches are super-great, imo.