Changes between Version 119 and Version 120 of TracMercurial

Timestamp:

May 21, 2022, 9:45:37 AM (2 years ago)

Author:

figaro

Comment:

Remove mention to unsupported version

TracMercurial

@@ -241 +241 @@
 Finally, the branch: prefix has a special meaning, as this will not select the specified revision, but the head which is reachable from that revision.
 
-=== TracBrowser changes in [milestone:0.11]
-
-The TracBrowser ''View revision'' form has been extended with pulldown menus for jumping to a given tag or branch. In Mercurial, a branch within a repository corresponds to a head, ie a changeset without children: 
+=== TracBrowser
+
+The TracBrowser ''View revision'' form has pulldown menus for jumping to a given tag or branch. In Mercurial, a branch within a repository corresponds to a head, ie a changeset without children: 
 
 [[Image(hg-plugin-browser.png, width=666px, border=2)]]
@@ -283 +283 @@
 Support for the Forest extension for Mercurial. Forest extension allows operations on trees with nested Mercurial repositories, called forests. Those to some degree correspond to multi-project CVS/Svn/... repositories.
 
-Already most of it is working, expect that it's hackish in the Trac 0.10.3 version of the plugin. Since it needs a bit more flexibile templating (in regards with the lookup/url's) this is hacked around node.path at the moment. Some (small/large?) issues remain but most of it is working.
+Already most of it is working, expect that it's hackish in the Trac 0.10.3 version of the plugin. Since it needs a bit more flexible templating (in regards with the lookup/url's) this is hacked around node.path at the moment. Some (small/large?) issues remain but most of it is working.
 
 Note that with the MultipleRepositorySupport branch of Trac, it should be possible to implement an IRepositoryProvider component knowing about the `forest` extension and adding besides the repository for the forest itself, the managed repositories as well.