Changes between Version 1 and Version 2 of InterTrac
- Timestamp:
- 2008-02-26T19:44:04Z (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
InterTrac
v1 v2 37 37 == Examples == 38 38 39 {{{40 #!comment41 Besides the other environments run by the same server process42 (called ''sibling'' environments), which are automatically detected,43 Support for sibling environments has been disabled.44 See http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/15745 }}}46 47 39 It is necessary to setup a configuration for the InterTrac facility. 48 40 This configuration has to be done in the TracIni file, `[intertrac]` section. … … 57 49 # -- Link to an external Trac: 58 50 trac.title = Edgewall's Trac for Trac 59 trac.url = http://projects.edgewall.com/trac 60 trac.compat = false 51 trac.url = http://trac.edgewall.org 61 52 }}} 62 53 … … 69 60 70 61 Finally, the `.compat` option can be used to activate or disable 71 a ''compat bility'' mode:62 a ''compatibility'' mode: 72 63 * If the targeted Trac is running a version below milestone:0.10 73 64 (r3526 to be precise), then it doesn't know how to dispatch an InterTrac … … 94 85 * `trac:log:@3300:3330` trac:log:@3300:3330 95 86 * `[trac 3300:3330]` [trac 3300:3330] 87 * finally, to link to the start page of a remote trac, simply use its prefix followed by ':', inside an explicit link. Example: `[th: Trac Hacks]` (''since 0.11; note that the ''remote'' Trac has to run 0.11 for this to work'') 96 88 97 89 The generic form `intertrac_prefix:module:id` is translated … … 102 94 103 95 ---- 104 === Discussion ===105 106 I think that the `trac` prefix could even be set as a default in the `[intertrac]` TracIni section. --CB107 108 ----109 96 See also: TracLinks, InterWiki