tigefa4u projects Trac

TracRevisionLog: log TracLinks are now able to deal with range boundaries specified in arbitrary order.

Before, ![1234:1000] would produce an empty range and the displayed revision log would start at ''head'', not very intuitive.

0.11.6dev: Python 2.3 compatibility fix for previous changeset.

TracRevisionLog: when `revs` is specified, strictly respect it, even if it's a range containing a single changeset.

The log: TracLinks had to be adapted accordingly and now they only set `revs` if the TracLinks actually specified a range, otherwise they use `rev`.

TracRevisionLog: Refactor `LogModule.process_request` so that `revranges` is None when no `revs` parameter is given.

TracRevisionLog: in path history mode, the revision row for a delete change had wrong version and changeset links.

TracRevisionLog: in path history mode, we should no keep increased indenting depth after each delete.

Also fixed the indentation of the first test.

#8459: fix a glitch in `get_copy_ancestry`, `fs.copied_from` got called twice.

Add unit-tests for `SubversionNode.get_branch_origin()` introduced in the previous changeset.

svn:mergeinfo renderer: optimize algorithm for computing eligible range.

We first try to get a minimal eligible range by finding the source branch revision origin, then removing the already merged revs and the blocked ones, and call `_get_node_revs` last. That costly call is restricted within the eligible range obtained so far, and is even avoided completely if the eligible range is already empty at that point.

See #8459.

TracRevisionLog: avoid getting a revision 0, which is not supported.

Fixes #8432.