Upcoming improvements of the Mercurial Bookmarks extension
As I’ve just spotted, some important additions have been committed to the repository
of the bookmarks extension: Push now supports only pushing non-bookmarked changesets, which means that your local bookmark branches are really only local and won’t be available in the target repository. And we have a corresponding feature in log to only show bookmarked changesets. Moreover, the bookmark you’re on is now tracked, so now the behaviour is more like the git local branches one.
Especially the push enhancement is important as you now don’t have to strip all bookmark-branches before pushing. So now we only need a means, to propagate bookmarks between repositories :-).
Update: Was backed out again :(.
Verwandte Artikel:
- Bookmarks, a.k.a. local branches in MercurialEclipse
- Mercurial Eclipse 1.2 has been released
- Rebase and subversion support in MercurialEclipse
Dezember 7th, 2008 in
computer, mercurial | tags: bookmarks, distributed, distributed revision control, distributed source control, dvcs, git, mercurial, revision control, source control, vcs
I’m so sorry that those changesets had to be backed-out because of some discussion in IRC . We came to the conclusion that this is no the right way to fix those things :/
Too bad – I really would have appreciated it, as this is a major point hindering adoption. So what kind of solution did you guys decide on? And will you implement it or will somebody else do so?
well we actually decided that we want to use some more generic option do allow pushing/pulling heads, so the non-bookmarked option was backed out.
What we kept was the including of bookmark names in log, and the track.current option, so those will be in 1.2.
So I wonder, who’ll tackle the wire protocol – it would open up a lot of possibilities for extensions if metadata could be synched.