News for hackers. Stuff that matters.
Re:Scaling Mercurial at Facebook by tonfa on Wednesday January 08, 2014 @03:00AM (#7022324)
I think you are confused, git and hg branches are very similar (I'd try to help but I'm not sure what the confusion is).
Re:Scaling Mercurial at Facebook by ahomescu1 on Wednesday January 08, 2014 @04:41AM (#7022577)
It's simple: I created a local branch, worked on it, then tried the git workflow:

1. Switch to the default branch

2. Cherry-pick (with the equivalent hg command) my changes from my own branch into default

3. Push the changes to the remote repo

What happened was that my local branch got pushed to the server, along with the default one. With git this wouldn't happen, it would push the local master to the remote master.

Re:Scaling Mercurial at Facebook by tonfa on Wednesday January 08, 2014 @05:09AM (#7022661)
Yes, by default all branches are pushed, (you would have to use --force if it creates new heads, and --new-branch to push new named branches). But I really don't see how it makes anything "server" or "client" side.

(and you could in any case decide to push just default: hg push -r default)

Re:Scaling Mercurial at Facebook by 16bytes on Wednesday January 08, 2014 @12:27PM (#7024896)
This is because hg pushes all changesets by default. There are two workflows in hg that would get you what you want:

hg push -b default

Pushes only changesets from the default branch. You can also do these with phases by marking your branch as private.