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

[Adrian Klaver]

On 02/05/2015 11:55 PM, Jaikiran Pai wrote:

>
> 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. I think what I'm getting to is that, having a standard default
> way to isolate/scope commits to the local bookmark and be assured that
> those won't end up to remote repo (unless explicitly done) is much more
> preferable, instead of expecting every developer in the team to be using
> the -s option, IMO.


Basically I think of bookmarks as a floating tag that moves with but is 
not locked to the underlying changeset(s). In other like words like its 
namesake, it marks your place but does not actually change what it is 
marking. So you are actually working with two things, the bookmark and 
the changeset.  At any rate, below are two blogs that helped me with 
branching/bookmark in Mercurial.

This one is not entirely current, but it is a good starting point.:

http://stevelosh.com/blog/2009/08/a-guide-to-branching-in-mercurial/


This is one is a fairly detailed suggested branching model:

http://draketo.de/light/english/mercurial/complete-branching-strategy

>
> -Jaikiran


-- 
Adrian Klaver
adrian.klaver at aklaver.com