Ideas for qgit

Hi, Marco!

As promised, here's what I would like to see in qgit:

1) Bookmarks or quick tags (qtags).  It may be useful to mark some
commits to make it easier to navigate qgit.  Yet I don't want them to
mix with real tags.  Perhaps qgit could save them separately, e.g.
in .git/refs/qtags to facilitate navigation.  qtags should appear
separately in the popup menu.

2) The "Patch" tab should be redesigned so that the diff can be shown
against the parent or against head/tag/qtag.  Users are not supposed to
enter SHA1.  If they have to, then it only confirms that qgit needs
qtags.

3) It would be nice to have some minimal navigating capabilities on the
Patch tab.  At least it should be possible to go up and down the
revision list and go to any head/tag/qtag/stgit patch.  It would
eliminate the need to switch to the "Rev list" too often.

4) Some bisect support would be nice, at least as good as in gitk.
Actually, I'm not using bisect too much, but it's probably because I'm
not debugging Wine these days.  Everything else is intelligible :-)

5) Branch view based on reflog.  Probably there should be an interface
allowing to limit the displayed revisions to one branch.  I think qgit
should still load all revisions that it loads now, but if users start
complaining about performance too much, maybe qgit should have an option
to load only the logged branch.  The problem is that some parents will
be unavailable in the view.

6) Try to unload some stuff from the popup menus to the main menu.  It
will be too log if we use it for tags, qtags, branch heads and branch
logs.

7) qgit command line should be documented.  "qgit --help" should display
help on stdout.

That said, qgit is in a pretty decent shape right now (except the "macro" interface, but I'm sure it will be improved before the next release). I actually used qgit as an important argument for one project to go with git rather than with Subversion of Mercurial. qgit for Mercurial would be cool, but I'd leave it to Mercurial fans.