#276 Mercurial bookmarks

[Gavin Lambert]

The web-based fork/merge-request system appears to be designed primarily with Git in mind, and doesn't seem to mesh well with Mercurial.

In particular the following features appear to be missing:
- displaying bookmarks
- performing merge requests based on bookmarks
- hiding closed branches from the top-level web interface (you should have to go into "more branches" and possibly even tick something before they're shown)

This is particularly unfortunate since as far as I can tell Mercurial bookmarks are the closest equivalent to Git branches, and the concept most suited to the "merge request" model of "fork, branch, one or two commits, merge request, delete branch after merged" (where for Mercurial you would use a bookmark instead of a branch, as an hg branch is a more permanent concept that's nearly impossible to delete).

It's possible I'm missing something, as I'm fairly new to Mercurial, but neither branches nor tags seem suited to this workflow.