| 2009-12-16 10:15:53 |
Andrew Schulman |
description |
Our trac-bzr install points to a plain directory which contains several shared repositories. In each of these shared repositories are a number of related branches. This is the same as in #264734, although I'm not sure this bug is related to that one.
In wiki pages and bug reports, trac links to changesets don't work. To refer to a changeset in trunk, I should be able to use e.g. [200/trunk] or changeset:200/trunk . But when I try either of these, the resulting text isn't a link. It's grey, and when I hover my mouse over it, the tooltip says "No changeset 200 in repository".
I've tried also just r200 or changeset:200, but those don't work either. That's as expected, since the branch would need to be specified.
Thanks,
Andrew. |
Our trac-bzr install points to a plain directory which contains several shared repositories. In each of these shared repositories are a number of related branches. This is the same as in #264734, although I'm not sure this bug is related to that one.
In wiki pages and bug reports, trac links to changesets don't work. To refer to a changeset in trunk, I should be able to write e.g. [200/trunk] or changeset:200/trunk . But when I try either of these, the resulting text isn't a link. It's grey, and when I hover my mouse over it, the tooltip says "No changeset 200 in repository".
I've also tried using just r200 or changeset:200, but those don't work either. That's as expected, since the branch name would need to be specified.
Thanks,
Andrew.
|
|
