Changes between Version 42 and Version 43 of TracMercurial

Timestamp:

Feb 4, 2008, 2:04:37 PM (16 years ago)

Author:

Christian Boos

Comment:

Mention the support for the Mercurial Queue extension and a few fixes

TracMercurial

@@ -86 +86 @@
 Note: 
  - the 0.12 version is somewhat experimental at this point ''worksforme''
+ - 0.9.1 was reported not to work with the 0.11 version of the plugin
  - 0.9.4 (and probably quite a few intermediate changesets between 0.9.3 and 0.9.4) interferes badly with the TH:AccountManager plugin when using Python 2.3.5. 
 It's not unlikely that other setups can be affected by the problem, as basically any code that relies on trapping the `ImportError`, after the `mercurial.demandimport` mechanism has been activated, will fail.
@@ -120 +121 @@
 === Setting up the mercurial plugin ===
 
-The TracMercurial-0.2 plugin egg should be added to the `plugins` folder of the 
+The TracMercurial plugin egg should be added to the `plugins` folder of the 
 environment, or it can be globally installed (`python setup.py install`
 or a `python setup.py develop`).
@@ -216 +217 @@
 notation of hg changesets. E.g `[8ef2]` would link to the changeset 
 8ef2ba892518c115170398ec754bd1c27cab271f ...
+Plain changeset numbers are also recognized, provided they are long enough (12 to 40).
 Also, it is possible to refer to changesets using the changeset: prefix 
 (or cset: or chgset:, for hgweb compatibility). 
@@ -237 +239 @@
 [[Image(wiki:ChristianBoos:blame-screenshot2.png)]]
 
+=== Mercurial Queue ===
+
+Since r6443, the MQ extension is supported. If you happen to have applied mq patches in your repository, Trac will show the corresponding patch names as '''Tags:''' in the changeset view.
+
+Also, with the 0.12 branch of the plugin (and the MultipleRepositorySupport branch of Trac), you can browse jointly the main repository and the repository for the associated Mercurial queue, if any (i.e. if you versioned your patch queue using `hg qinit -c` and `hg qcommit`). Furthermore, if you declare such a mercurial repository to be a MQ repository, then all the patches will be correctly rendered as patches, regardless of the patch name (see r6462 for details).
+
 == Bugs and Limitations ==
 
@@ -314 +322 @@
 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.
 
- ''Note that with the MultipleRepositoryBranch 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.''
+ ''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.''
 
 ==== ''Add your cool feature here...'' ====