Changes between Version 2 and Version 3 of 0.12/TracLinks
- Timestamp:
- Feb 10, 2010, 12:44:08 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
0.12/TracLinks
v2 v3 241 241 242 242 === ticket: links === 243 ''aliase:'' bug: 243 244 244 245 Besides the obvious `ticket:id` form, it is also possible to specify a list of tickets or even a range of tickets instead of the `id`. This generates a link to a custom query view containing this fixed set of tickets. … … 268 269 === Version Control related links === 269 270 ==== source: links ==== 271 ''aliases:'' browser:, repos: 270 272 271 273 The default behavior for a source:/some/path link is to open the directory browser 272 if the path points to a directory and otherwise open the log view.274 if the path points to a directory or to show the latest content of the file. 273 275 274 276 It's also possible to link directly to a specific revision of a file like this: … … 282 284 Finally, one can also highlight an arbitrary set of lines: 283 285 - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103. 284 ''(since 0.11)'' 286 ''(since 0.11)'' 287 288 Note that in presence of multiple repositories, the name of the repository is simply integrated in the path you specify for `source:`. 285 289 286 290 ==== export: links ==== … … 311 315 Finally, note that in all of the above, a revision range can be written indifferently `x:y` or `x-y`. 312 316 317 Again, in the presence of multiple repositories, the name of the repository should come first and be integrated in the path, e.g. `log:repos/branches` or `[20-40/repos]`. 318 313 319 ---- 314 320 See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki