Changes between Version 1 and Version 2 of TracLinks


Ignore:
Timestamp:
11/17/04 15:27:55 (20 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracLinks

    v1 v2  
    88ticket, report and changeset numbers in the following notation:
    99{{{
    10  * Ticket #1
    11  * Report {1}
    12  * Changeset [1]
    13  * File svn:trunk/COPYING.
     10 * Ticket #1 or ticket:1
     11 * Report {1} or report:1
     12 * Changeset [1] or changeset:1
     13 * File source:trunk/COPYING.
    1414}}}
    1515Display:
    16  * Ticket #1
    17  * Report {1}
    18  * Changeset [1]
    19  * File svn:trunk/COPYING.
    20  
     16 * Ticket #1 or ticket:1
     17 * Report {1} or report:1
     18 * Changeset [1] or changeset:1
     19 * File source:trunk/COPYING.
     20
     21Trac links can also be given a custom link title like this:
     22{{{
     23[ticket:1 This is a link to ticket number one].
     24}}}
     25
     26Display:
     27
     28[ticket:1 This is a link to ticket number one].
     29
    2130It seems a simple enough concept at a glance, but actually allows quite a complex network of information.
    2231
    2332In practice, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's happening in a project or why a particular change was made.
     33
     34== source: links ==
     35
     36The default behavior for a source:/some/path link is to open the directory browser if the path points
     37to a directory and otherwise open the log view. It's also possible to link directly to a specific
     38revision of a file like this: source:/some/file#123 or like this to link to the latest revision:
     39source:/some/file#latest.
    2440
    2541== Where to use TracLinks ==