Changes between Version 103 and Version 104 of TracMercurial

Timestamp:

Dec 8, 2015, 12:03:13 PM (8 years ago)

Author:

figaro

Comment:

Cosmetic changes

TracMercurial

@@ -1 +1 @@
 [[PageOutline(2-3)]]
 
-= Mercurial Plugin for Trac (#1847)
-
-This a plugin for Trac which enables [http://www.selenic.com/mercurial Mercurial] to be used as the VersionControlSystem for Trac.
+= Mercurial Plugin for Trac
+
+This a plugin for Trac which enables [http://www.selenic.com/mercurial Mercurial] to be used as the VersionControlSystem for Trac. It was originally developed under #1847.
 
 Please use a recent version of the plugin before reporting issues.
@@ -83 +83 @@
    python setup.py bdist_egg
    }}}
- - Install it in the current Python (or [http://pypi.python.org/pypi/virtualenv virtualenv]) installation:
+ - Install it in the current Python (or [pypi:virtualenv virtualenv]) installation:
    {{{#!sh 
    python setup.py install
@@ -100 +100 @@
 ==== Windows
 
-On Windows, it looks like it's possible to re-use the Mercurial library coming from the [Mercurial:BinaryPackages installer], 
-see [http://selenic.com/pipermail/mercurial/2007-July/013827.html this mail].
+On Windows, it looks like it is possible to re-use the Mercurial library coming from the [Mercurial:BinaryPackages installer], see [http://selenic.com/pipermail/mercurial/2007-July/013827.html this mail].
 However, it is not possible to achieve this using PYTHONPATH and PATH: it fails with `ImportError: No module named handlers` due to library.zip coming in the sys.path before the standard library.
 
@@ -117 +116 @@
 === Setting up the Mercurial plugin
 
-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`. For general instructions about plugins, see also TracPlugins.
-
-If you installed the egg globally and you're modifying an existing Trac environment to use the Mercurial backend, then you have to explicitly ''enable'' the plugin in TracIni.
+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`. For general instructions about plugins, see also TracPlugins.
+
+If you installed the egg globally and you're modifying an existing Trac environment to use the Mercurial backend, then you have to explicitly '''enable''' the plugin in TracIni.
 
 Since the version 0.11 of the plugin, the package has been renamed to `tracext`:
@@ -161 +160 @@
 {{{#!ini
 [hooks]
-; If mercurial-plugin is installed globally
+# If mercurial-plugin is installed globally
 commit = python:tracext.hg.hooks.add_changesets
 changegroup = python:tracext.hg.hooks.add_changesets
 
-; If mercurial-plugin is installed in a Trac plugins directory
+# If mercurial-plugin is installed in a Trac plugins directory
 commit = python:/path/to/hooks.py:add_changesets
 changegroup = python:/path/to/hooks.py:add_changesets
@@ -185 +184 @@
 == Features
 
-Mercurial support is basic, but works well. I've tested that on the Mercurial repository itself and the performance is acceptable, even if there's currently ''no'' caching in the database, see #8417.
+Mercurial support is basic, but works well and has been tested on the Mercurial repository itself. The performance is acceptable, even if there is currently no caching in the database, see #8417.
 
 For those used to Subversion in general and Subversion repository browsing in Trac in particular, there are a few differences worth noting.
@@ -214 +213 @@
 === 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, i.e. a changeset without children: 
+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: 
 
 [[Image(hg-plugin-browser.png,width=666px,align=center)]]
@@ -224 +223 @@
 === 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).
+Since r6443, the MQ extension is supported. If you 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, ie 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).
 
 ==== Visualize branches and merges
@@ -232 +231 @@
 There should be a way to show graphically the branch and merge points within the revision log view. Not something as fancy as `hgk`, but nonetheless something that will make the changeset relationships immediately obvious.
 
-''Starting with Trac [milestone:0.13], we show a graphical overview of the branch graph when viewing the log of the repository root (#1492)''
-
-Also, there is [http://trac-hacks.org/wiki/RevtreePlugin RevtreePlugin].
+Starting with Trac [milestone:0.13], we show a graphical overview of the branch graph when viewing the log of the repository root (#1492).
+
+Also, there is the [th:RevtreePlugin].
 
 ==== Search over the source
@@ -257 +256 @@
 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 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.''
+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 requested feature here
@@ -279 +278 @@
 === Troubleshooting 
 
-==== "unsupported version control system hg" 
+==== "Unsupported version control system hg" 
 
 If you get this message try the following two basic checks first:
@@ -286 +285 @@
   {{{#!pycon
 >>> from mercurial import ui, hg
->>> repo = hg.repository(ui.ui(), '/path/to/a/mercurial/repo')
+>>> repo = hg.repository(ui.ui(), '/path/to/mercurial/repo')
 >>> len(repo)
 234
   }}}
-  You can also look at the `hg.__file__` attribute to verify you're loading the expected Mercurial library.
+  You can also look at the `hg.__file__` attribute to verify you are loading the expected Mercurial library.
 
  * Log in as an user with `TRAC_ADMIN` permission, and look in the `Admin` pages, `General / Plugins`. Do you see the entry for the !TracMercurial plugin there? If yes, is the !MercurialConnector component enabled? 
@@ -307 +306 @@
 I'm interested in feedback concerning the code, in particular concerning Mercurial. I'm pretty sure I did things in a sub-optimal way, as I was discovering the guts of hg while writing the plugin.  Therefore, I'll be pleased to get tips for improvements.
 
-'' -- ChristianBoos ''
+ -- ChristianBoos