Branching and remote heads in Mercurial
Posted
by hekevintran
on Stack Overflow
See other posts from Stack Overflow
or by hekevintran
Published on 2010-04-07T09:29:00Z
Indexed on
2010/04/07
9:33 UTC
Read the original article
Hit count: 226
I created a new branch using this command: hg branch new_branch
After the first commit to the new branch, the default branch becomes inactive. If this is pushed the central repository will have only one head which belongs to the new branch.
When my colleague pushes his commits on the default branch, he will get this error: pushing to ssh://... searching for changes abort: push creates new remote heads! (did you forget to merge? use push -f to force)
Is there anything bad about forcing the push? Why are remote heads bad?
How do you work remotely on separate branches and push to one repository?
© Stack Overflow or respective owner