Changes between Version 104 and Version 105 of TracMercurial
- Timestamp:
- Jan 18, 2016, 2:35:35 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracMercurial
v104 v105 1 [[PageOutline(2- 3)]]1 [[PageOutline(2-5,Contents)]] 2 2 3 3 = Mercurial Plugin for Trac … … 66 66 === Trac 67 67 68 Consult the version table [#Releases below]to check which version you need for your version of Trac. If you want to get a specific revision, add an `svn up -rxxx` step to the instructions below, after the checkout.68 Consult the version table to check which version you need for your version of Trac. If you want to get a specific revision, add an `svn up -rxxx` step to the instructions below, after the checkout. 69 69 70 70 Installation of the plugin, depending on the version of Trac you are using: … … 118 118 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. 119 119 120 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.120 If you installed the egg globally and you are modifying an existing Trac environment to use the Mercurial backend, then you have to explicitly '''enable''' the plugin in TracIni. 121 121 122 122 Since the version 0.11 of the plugin, the package has been renamed to `tracext`: … … 193 193 194 194 In Mercurial, the ''Previous Changeset''/''Next Changeset'' navigation is ''not'' purely sequential, as it is in Subversion. 195 Instead of a ''flat'' history of successive changesets, we actually navigate a [ http://en.wikipedia.org/wiki/Directed_acyclic_graph DAG] of changesets.195 Instead of a ''flat'' history of successive changesets, we actually navigate a [wikipedia:Directed_acyclic_graph DAG] of changesets. 196 196 This means a changeset can have multiple parents (0, 1 or 2) and multiple children as well (0 to n). 197 197 … … 241 241 ==== Highlight Conflict Resolution 242 242 243 While visualizing changeset diffs for merge changesets, we already show the changes relative to both parents, which helps to understand how conflicts (if any) were solved. But this can be improved by specifically highlighting lines that differ sfrom both parents.243 While visualizing changeset diffs for merge changesets, we already show the changes relative to both parents, which helps to understand how conflicts (if any) were solved. But this can be improved by specifically highlighting lines that differ from both parents. 244 244 245 245 ==== Repository Management … … 264 264 == Bugs and Limitations 265 265 266 === Features that Trac+svn has but not currently implemented forTrac+hg266 === Features in Trac+svn but not in Trac+hg 267 267 268 268 * No ''path history'' mode, ie show all create/delete operations that affected a given path. … … 304 304 - [mercurial:CommandServer] and [mercurial:PythonHglib] (not yet used - see #10411) 305 305 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. 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. 307 307 308 308 -- ChristianBoos