hg 和 Git 在多人协作上有哪些差别, 怎样理解?

Question

Pygments 项目是用 hg 管理的, 提交了一次 PR, 又想提交第二次,
按照 Git 的思路, 我再合并之前应该同步对方的更新, 再修改和提交,

经过搜索, 我执行了:

hg pull <url>
hg update

这样 default 分支就完成了更新,
然而搜索当中, 我并没有看到和 Git 那样的分支处理,
比如 git push origin feature-a 这样的功能, hg 当中并没细写.

hg 在多个账户协作的模型上和 Git 是有怎样的不同呢?

Answer 1

Branch in hg is not as cheap as git. Under hg, branches like feature-a are generally not used, but branches like stable, unstable, 2.0, and 3.0 are used. In other words, the branch in hg is a persistent branch, unlike git which has a cheap local branch.

But git’s lightweight local branch is so easy to use, hg is also jealous of it. So later, hg implemented similar functions in the form of bookmarks plug-in, and after stabilization, it was incorporated into the main body of hg. See http://mercurial.selenic.com/wiki/Bookmarks/

for details

I haven’t been a mercury fan for many years, so I apologize for any mistakes.