Edgewall Software

Changes between Version 42 and Version 43 of TracMercurial


Ignore:
Timestamp:
Feb 4, 2008, 2:04:37 PM (15 years ago)
Author:
Christian Boos
Comment:

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

Legend:

Unmodified
Added
Removed
Modified
  • TracMercurial

    v42 v43  
    8686Note:
    8787 - the 0.12 version is somewhat experimental at this point ''worksforme''
     88 - 0.9.1 was reported not to work with the 0.11 version of the plugin
    8889 - 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.
    8990It'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.
     
    120121=== Setting up the mercurial plugin ===
    121122
    122 The TracMercurial-0.2 plugin egg should be added to the `plugins` folder of the
     123The TracMercurial plugin egg should be added to the `plugins` folder of the
    123124environment, or it can be globally installed (`python setup.py install`
    124125or a `python setup.py develop`).
     
    216217notation of hg changesets. E.g `[8ef2]` would link to the changeset
    2172188ef2ba892518c115170398ec754bd1c27cab271f ...
     219Plain changeset numbers are also recognized, provided they are long enough (12 to 40).
    218220Also, it is possible to refer to changesets using the changeset: prefix
    219221(or cset: or chgset:, for hgweb compatibility).
     
    237239[[Image(wiki:ChristianBoos:blame-screenshot2.png)]]
    238240
     241=== Mercurial Queue ===
     242
     243Since 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.
     244
     245Also, 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).
     246
    239247== Bugs and Limitations ==
    240248
     
    314322Since 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.
    315323
    316  ''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.''
     324 ''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.''
    317325
    318326==== ''Add your cool feature here...'' ====