Why did "hg push", push my local bookmark to remote?

[Jaikiran Pai]

On Saturday 07 February 2015 06:50 AM, Ryan McElroy wrote:
>
>>> From what I understand of that proposal, it sounds
>>> like I would be able to do in hg what I currently can do with local
>>> lightweight branches in git like:
>>>
>>> git checkout local-branch-foo
>>> ... // do changes
>>> git commit -m "WIP commit locally"
>>> git push upstream master // i.e. *don't* push local-branch-foo but only
>>> push the branch named master to upstream remote repo
>>> ... // more changes to local branch and now ready to have it 
>>> included in
>>> master branch
>>> git rebase upstream/master // rebase my local branch commits on top of
>>> upstream master branch
>>> git push upstream master // now that the local commits are ready to be
>>> pushed to upstream and are rebase on (local) master branch, push it to
>>> the remote master branch
>> This is probably behavior we could experiment with in the remotenames
>> extension. Thoughts, Ryan?
> The remote bookmarks feature in the remotenames extension is, in my 
> opinion, heavily influenced by the "good" parts of git's remote 
> branches: eg, not moving anything when pulling, and pushing only what 
> you want, so I think this is a good thing to base our behavior on.
>
> Cheers,
>
> ~Ryan

 From what I gather, this is an enhancement that's being planned in 
remotenames extension and isn't available for production use yet? Is 
there some place where I can checkout the doc and try it out if it's in 
a beta state? It's more out of curiosity and providing feedback rather 
than trying to use it in my day to day work.

-Jaikiran