Changes between Version 16 and Version 17 of TracGit
- Timestamp:
- Mar 9, 2015, 8:57:02 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracGit
v16 v17 2 2 = Git support in Trac 3 3 4 Starting with version [milestone:1.0], Trac features built-in support 5 for [http://git-scm.com/ Git] so that it can be used as one of the 6 VersionControlSystem for Trac. 4 Since version [milestone:1.0], Trac features built-in support 5 for [http://git-scm.com/ Git] as a VersionControlSystem for Trac. 7 6 8 7 Please note that we're still considering the level of performance to … … 12 11 == Features 13 12 14 * Browsing source code in a Git repositoryvia the TracBrowser13 * Browsing source code via the TracBrowser 15 14 * Viewing the change history of a file or directory using TracRevisionLog 16 * Performing diffs between any two files or twodirectories17 * Displaying submittedchanges in the TracTimeline15 * Performing diffs between any two files or directories 16 * Displaying changes in the TracTimeline 18 17 * (Optionally) caching TracChangeset information in Trac's database 19 18 * Caching Git commit relation graph in memory 20 * Using the TracSearch page to search change descriptions19 * Search change descriptions via TracSearch 21 20 * Annotation support, also known as "blame" operation 22 21 * Interpretation of 40-character wide hex-strings as sha1 commit checksums … … 28 27 [http://git-scm.com/download Git:Download]. 29 28 30 We try to maintain backward compatibility with versions of Git as old as 1.5.6,31 up to the latest. Better use a recent versionhowever.29 We try to maintain backward compatibility with versions of Git from 1.5.6 to the latest. 30 It's better use a recent version, however. 32 31 33 32 === Configuration … … 39 38 40 39 Note that the repository should be made accessible as a local repository. 41 Thanks to the distributed nature of Git, that's always possible (if the42 repository is not already local, simply `git clone` it ).40 Thanks to the distributed nature of Git, that's always possible. If the 41 repository is not already local, simply `git clone` it. 43 42 44 43 == Trac … … 66 65 - for the ''repository type'', specify `git` instead of the default `svn`. 67 66 - for the ''repository directory'', specify the location of the Git repository 68 ( including the ending`.git` directory).67 (for Trac < 1.0.2 the path of a non-bare repository will end in a `.git` directory). 69 68 70 69 Your [wiki:TracIni <trac_environment>/conf/trac.ini] configuration file … … 85 84 86 85 87 Also in there, make sure you specify the location of the `git` executable, in case it's not the default `/usr/bin/git`. As an example, for Windows:86 Specify the location of the `git` executable, in case it's not the default `/usr/bin/git`. As an example, for Windows: 88 87 {{{#!ini 89 88 [git] … … 95 94 96 95 If all you need is to work with a single git environment, it is enough 97 to modify the `[ trac]` section in your [TracIni trac.ini] so that it98 contains the appropriate values for the ` repository_type` and99 ` repository_dir` options, like in the above example.96 to modify the `[repositories]` section in your [TracIni trac.ini] so that it 97 contains the appropriate values for the `.type` and 98 `.dir` options, like in the above example. 100 99 101 100 However, if you need more than one git repository, or if you want to … … 104 103 contained in that repository, you can add non-default repositories. 105 104 106 There is basically two ways to do it, either via the105 There are basically two ways to do that, either via the 107 106 [TracIni#repositories-section "[repositories]"] section of the TracIni 108 107 file, or via the web administration interface using the
