tag:blogger.com,1999:blog-3157881265969801285.post1225817398712680345..comments2019-06-21T17:31:27.462-04:00Comments on b.ling on software development: Working in Git to Working in MercurialAnonymoushttp://www.blogger.com/profile/12728014380144489730noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3157881265969801285.post-7155163980043906792013-06-10T08:05:20.191-04:002013-06-10T08:05:20.191-04:00mercurial bookmarks only move forward with commits...mercurial bookmarks only move forward with commits, <b>not</b> with pulls.<br /><br />you are of course welcome to create a master bookmark, but you'd have to manually update the bookmark to the tip after every pull for it to be truly equivalent to git.<br /><br />the workflow you mentioned is very tedious to do in mercurial, and than rather tracking master yourself it is often easier just to do 'hg book -r 123' if you truly need that branch to be directly off of "master".Anonymoushttps://www.blogger.com/profile/12728014380144489730noreply@blogger.comtag:blogger.com,1999:blog-3157881265969801285.post-88985606922380693652013-06-10T05:06:51.309-04:002013-06-10T05:06:51.309-04:00I disagree with "no need for a git master equ...I disagree with "no need for a git master equivalent". A typical workflow would be: <br /><br />1) book and work on "feature-1" <br />2) go back to "master" (whoops, no reference?!) <br />3) book and work on "feature-2"schlamarhttps://www.blogger.com/profile/13806747860793542103noreply@blogger.com