Edgewall Software

Changes between Version 25 and Version 26 of InterTrac


Ignore:
Timestamp:
Jun 23, 2006, 5:41:23 PM (18 years ago)
Author:
Christian Boos
Comment:

Cleaned up a bit that page, removed most of the discussion (not relevant anymore)

Legend:

Unmodified
Added
Removed
Modified
  • InterTrac

    v25 v26  
    1616== Link Syntax ==
    1717
     18Simply use the name of the other Trac environment as a prefix,
     19followed by a colon, ending with the resource located in the other environment.
     20
    1821{{{
    1922<target_environment>:<TracLinks>
    2023}}}
    2124
    22 The link is composed by the target environment name,
    23 followed by a colon (e.g. `trac:`),
    24 followed by a regular TracLinks, of any flavor.
     25The other resource is specified using a regular TracLinks, of any flavor.
    2526
    2627That target environment name is either the real name of the
     
    7576   * `trac:changeset:1912` trac:changeset:1912
    7677   * `[T1912]` [T1912]
    77  * to the log range [3300:3330]: ''(Note: these ones will work at the next server upgrade)''
     78 * to the log range [3300:3330]: ''whoops, still doesn't work, why?''
    7879   * `trac:log:3300:3330` trac:log:3300:3330
    79    * `[trac 3300:3330]` [trac 3300:3330]
     80   * `[trac 3300:3330]` [trac 3300:3330] 
    8081
    8182The generic form `intertrac_prefix:module:id` is translated
     
    8889=== Discussion ===
    8990
    90   Note that the examples above are hard coded to appropriate destinations, '''not''' processed via InterTrac.  Specifically, the format of the links that rely on the remote quickjump are not as they will appear when generated by InterTrac.
    91 
    92 Thanks for the reminder.... It's fixed now: the examples are using the real thing.
    9391I think that the `trac` prefix could even be set as a default in the `[intertrac]` TracIni section. --CB
    9492
    9593----
    96   It would be great, if these links also work in changeset comments, and source code comments. This would facilitate tickets, which touch multiple source code repositories, and patches which can be applied to multiple trees, which a dedicated trac instance each, as it should be possible by using source code control systems like bazaar-ng and mercurial.
    97 
    98 ''worksforme'' (next time, I'll delete the above)
    99 
    100 ----
    10194See also: TracLinks, InterWiki