--- a/docs/index.rst Sun Jul 15 12:49:25 2012 +0200
+++ b/docs/index.rst Sun Jul 15 12:57:22 2012 +0200
@@ -77,11 +77,11 @@
You will probably want to use the associated version of hgview (qt viewer
recommended). ::
- $ hg clone http://hg-lab.logilab.org/wip/hgview/
+ $ hg clone http://hg-lab.logilab.org/wip/hgview/ -u obsolete
$ cd hgview
$ python setup.py install --user
-works with mercurial 2.1 and 2.2 (recommended)
+Works with mercurial 2.2
---
@@ -131,15 +131,6 @@
obs-road-map
-Known caveats
-=============
-
-Here is a list of known issues that will be fixed later:
-
-* Unstable changeset turn secret.
-
-* ``hg stabilize`` does not handle conflicts.
-
Known limitation and bug
=================================
@@ -161,29 +152,15 @@
* ``hg merge`` considers an extinct head to be a valid target, hence requiring
you to manually specify target all the time.
-* trying to exchange obsolete relations with a static http repo will crash.
+* trying to exchange obsolete marker with a static http repo will crash.
+
+* trying to exchange a lot of obsolete markers through http crash.
* Extinct changesets are turned secret by various commands.
* Extinct changesets are hidden using the *hidden* feature of mercurial only
supported by a few commands.
- Only ``hg log``, ``hgview`` and `hg glog` (2.2 only) support it. ``hg head`` or other visual viewer don't.
+ Only ``hg log``, ``hgview`` and `hg glog` support it. ``hg head`` or other visual viewer don't.
* hg heads show extinct changeset
-
-Fixed in 2.2
----------------------------------
-
-* hg graphlog show extinct changeset
-
-* Mercurial 2.1 think you are pushing additional heads even when the new head
- obsolete another one. You have to use hg push -f more often than necessary.
-
-
-* ``hg heads`` shows extinct changeset
-
-* ``hg merge`` considers an extinct head to be a valid target, hence requiring
- you to manually specify target all the time.
-
-* trying to exchange obsolete relations with a static http repo will crash.