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

[Scott Palmer]

> On Feb 6, 2015, at 2:55 AM, Jaikiran Pai <jai.forums2013 at gmail.com> wrote:
> 
>> On Friday 06 February 2015 01:12 PM, Jaikiran Pai wrote:
>> On Friday 06 February 2015 12:41 PM, Sean Farley wrote:
>>>> I however wish that it was much simpler than this and maybe that
>>>> proposal in that mercurial-dev thread from 2012 could be revisited to
>>>> improve the situation?
>>> That is moot as far as I understand. What would be considered now is a
>>> proposal to improve the 'paths' option to only push certain branches to
>>> specific remote servers.
>>> 
>>> I don't understand what you want to be easier. You are saying that
>>> adding *one* command-line option of '-s' to your secret branch is too
>>> hard? I find that very explicit and refreshing that Mercurial is doing
>>> what I told it to do: mark this secret. Commits on top of secret commits
>>> are always secret.

<snip>

> 
> To add to this earlier reply, IMO, it's not about having to add one command line option of -s. It's much more than that when there's more than 1 developer within a team. It's hard to enforce using the -s when it's not the default or when it involves having to carefully remember that you are on a local bookmark and commits to that bookmark should be secret.

You only have to remember that for the first commit to the branch. Commits on top of that will remain secret because they descend from a secret commit.

So you *don't* have to remember you are on a local bookmark after you have marked it secret.


Scott