Changes between Version 2 and Version 3 of TracLinks


Ignore:
Timestamp:
Apr 16, 2016, 7:07:21 PM (9 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracLinks

    v2 v3  
    337337 - `source:/some/file@123` - link to the file's revision 123
    338338 - `source:/some/file@head` - link explicitly to the latest revision of the file
     339 - `source:/some/file@named-branch` - link to latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial)
    339340
    340341If the revision is specified, one can even link to a specific line number:
    341342 - `source:/some/file@123#L10`
    342343 - `source:/tag/0.10@head#L10`
     344 - `source:/some/file@named-branch#L10`
    343345
    344346Finally, one can also highlight an arbitrary set of lines:
     
    354356 * `export:123:/some/file` - get revision 123 of the specified file
    355357 * `export:/some/file@123` - get revision 123 of the specified file
     358 * `export:/some/file@named-branch` - get latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial).
    356359
    357360This 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.
     
    367370 - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795
    368371 - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path
     372 - `log:/tools@named-branch` - the revisions in `tools` starting from the latest revision in `named-branch` (DVCS such as Git or Mercurial)
    369373
    370374There are short forms for revision ranges as well: