Changes between Version 12 and Version 13 of TracGit

Timestamp:

Aug 22, 2014, 5:24:38 AM (10 years ago)

Author:

Ryan J Ollos

Comment:

Mention versions in which two issues have been fixed. Use repository path rather than repository_dir, because the option is deprecated and will be removed soon.

TracGit

@@ -1 +1 @@
 [[PageOutline(2-3)]]
-= Git support in Trac (#10594) =
+= Git support in Trac (#10594)
 
 Starting with version [milestone:1.0], Trac features built-in support 
@@ -10 +10 @@
 repositories should be handled reasonably well, however.
 
-== Features ==
+== Features
 
 * Browsing source code in a Git repository via the TracBrowser
@@ -22 +22 @@
 * Interpretation of 40-character wide hex-strings as sha1 commit checksums 
 
-== Git ==
-=== Download and Installation ===
+== Git
+=== Download and Installation
 
 You need to have the `git` command line tools installed. You can download Git itself from 
@@ -31 +31 @@
 up to the latest. Better use a recent version however.
 
-=== Configuration ===
+=== Configuration
 
 The configuration has to be done mainly on the Trac side, 
@@ -42 +42 @@
 repository is not already local, simply `git clone` it).
 
-== Trac ==
+== Trac
 
 The Trac Git support is included with Trac since 1.0 as an optional component: `tracopt.versioncontrol.git`.
 
 You simply have to explicitly ''enable'' the plugin in TracIni:
-{{{
+{{{#!ini
 [components]
 tracopt.versioncontrol.git.* = enabled
@@ -55 +55 @@
 using the //General / Plugins// panel.
 
-=== Setting up a Trac environment ===
+=== Setting up a Trac environment
 
 You can either reuse an existing Trac environment,
@@ -70 +70 @@
 Your [wiki:TracIni <trac_environment>/conf/trac.ini] configuration file
 should have a `[trac]` section similar to the following:
-{{{
+{{{#!ini
 [trac]
 repository_type = git
@@ -76 +76 @@
 }}}
 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:
-{{{
+{{{#!ini
 [git]
 git_bin = C:/Dev/msysgit/bin/git.exe
@@ -105 +105 @@
 
 
-=== Setting up post-receive hooks === #hooks
+=== Setting up post-receive hooks #hooks
 
 If you want to benefit from some advanced features for your repository,
@@ -119 +119 @@
 You can then enable the CommitTicketUpdater functionality in your `trac.ini` by adding:
 
-{{{
+{{{#!ini
 tracopt.ticket.commit_updater.* = enabled
 }}}
@@ -127 +127 @@
 == Troubleshooting 
 
-* `repository_dir` in the configuration section needs to be the `.git` repository directory (i.e. the one containing the file `HEAD` and `config`), not the working tree directory that holds the `.git/` folder (#11297). 
-* Wrong permissions may also be the cause of the error `GitError: GIT control files not found, maybe wrong directory?`. Make sure the `repository_dir` argument is accessible via git by the `tracd` process. 
+* For Trac < 1.0.2, the `repository_dir` in the configuration section needs to be the `.git` repository directory (i.e. the one containing the file `HEAD` and `config`), not the working tree directory that holds the `.git` folder (#11297). However, a `bare` repository will have these control files in the top-level directory and will not contain a `.git` directory.
+* Wrong permissions may also be the cause of the error `GitError: GIT control files not found, maybe wrong directory?`. Make sure the repository path is accessible via git by the `tracd` process. 
 * If you are noticing a slow down in trac with a repository above 500 commits, try disabling the caching. It seems to bog things down as a repo grows(!)
 * Don't forget to enable the plugin:
-  {{{
+  {{{#!ini
   [components]
   tracopt.versioncontrol.git.* = enabled 
   }}}
-* If you don't see the `shortrev` and `commit` branch, you probably have caching enabled (`cached_repository = true, persistent_cache = true`). Set those to false.
-* The source browser can throw an error when trying to kill a git log process; it's not clear why it should be an error for the process to have completed.  This problem manifests as a stack trace with terminate_nix at the end (#10958).
+* If you don't see the `shortrev` and `commit` branch, you probably have caching enabled (`cached_repository = true`, `persistent_cache = true`). Set those to false.
+* For Trac < 1.0.2, the source browser can throw an error when trying to kill a git log process; it's not clear why it should be an error for the process to have completed.  This problem manifests as a stack trace with terminate_nix at the end (#10958).
 
 == Known Issues