Changes between Version 94 and Version 95 of TracLinks
- Timestamp:
- Aug 10, 2015, 11:14:46 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracLinks
v94 v95 338 338 - `source:/some/file@123` - link to the file's revision 123 339 339 - `source:/some/file@head` - link explicitly to the latest revision of the file 340 - `source:/some/file@named-branch` - link to latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial) 340 341 341 342 If the revision is specified, one can even link to a specific line number: 342 343 - `source:/some/file@123#L10` 343 344 - `source:/tag/0.10@head#L10` 345 - `source:/some/file@named-branch#L10` 344 346 345 347 Finally, one can also highlight an arbitrary set of lines: … … 355 357 * `export:123:/some/file` - get revision 123 of the specified file 356 358 * `export:/some/file@123` - get revision 123 of the specified file 359 * `export:/some/file@named-branch` - get latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial). 357 360 358 361 This can be very useful for displaying XML or HTML documentation with correct stylesheets and images, in case that has been checked in into the repository. Note that for this use case, you'd have to allow the web browser to render the content by setting `[browser] render_unsafe_content = yes` (see TracIni#browser-section), otherwise Trac will force the files to be downloaded as attachments for security concerns. … … 368 371 - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 369 372 - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path 373 - `log:/tools@named-branch` - the revisions in `tools` starting from the latest revision in `named-branch` (DVCS such as Git or Mercurial) 370 374 371 375 There are short forms for revision ranges as well: