4 ms·
Sadly bitbucket does not have very good support for features from "modern" mercurial like bookmarks and changeset evolution. Since most of their users are git
by ngoldbaum 12y ago
Sadly bitbucket does not have very good support for features from "modern" mercurial like bookmarks and changeset evolution. Since most of their users are git users I don't think they are strongly motivated to shore up mercurial support.
- jordigh 12y agoTheir devs hang out in #mercurial in Freenode and have been talking about how to implement Evolve on the bitbucket WUI.
- ngoldbaum 12y agoGood to know! I'm looking forward to more news on that front.
- bobmoretti 12y agoThe advantage of changeset evolution is obvious to me. But as a longtime Mercurial user, I don't grok the benefit of bookmarks. Do you have a simple example where a bookmark is more useful than a permanent branch?
- ngoldbaum 12y agoThe teams I work with don't like the permanence of mercurial named branches. Bookmarks are a nice lightweight alternative way to name a short-lived head rather than creating a permanent tag for a two-line commit. Before bookmarks we used anonymous heads.
- mrtngslr 12y agoIf you haven't already, then you can go vote on this issue: https://bitbucket.org/site/master/issue/6710/enable-exchange-of-obsolete-evolve-markers https://bitbucket.org/site/master/issue/6710/enable-exchange... -- and ask your collegues to do so too! :-) The Bitbucket devs are nice guys and have said that they do listen to issue feedback like this.