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

[Arne Babenhauserheide]

Am Freitag, 6. Februar 2015, 13:12:28 schrieb Jaikiran Pai:
> Sean, the thing I wish was easier was local/lightweight branches in 
> mercurial. As a developer working on various different features, bug 
> fixes locally I wish it's easier to just do a "hg up 
> local-branch/bookmark/or-whatever-other-term", then do some commits on 
> it and don't have to worry that those commits will end up remotely 
> unless I explicitly push them.

What you’re running into is a philosophical difference between Mercurial and Git.


- In Git all the repos are completely separate and you have to connect them by hand.
- In Mercurial all the repos are part of the project, and you have to separate them by hand.


Different from you, I want all commits I do to end up remotely when I push, so others can check them. A bookmark tells others that it might be a bad idea to use intermediate changes, but it does not decouple my repo from theirs.

To decouple my repo I have to explicitly use phases: hg phase --force --secret .

(. is what I’m working on right now)


Git formed your expectations to think that you’re always disconnected, except if you connect yourself.

Mercurial keeps you more connected: You’re part of the team and create a shared history. What you have locally is mostly what the whole project sees. You know what the others see which makes it easier to communicate.


Best wishes,
Arne
-- 
1w6 sie zu achten,
sie alle zu finden,
in Spiele zu leiten
und sacht zu verbinden.
→ http://1w6.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 299 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20150206/04a49100/attachment.asc>