Edgewall Software

Changes between Version 22 and Version 23 of TracGit


Ignore:
Timestamp:
Jun 2, 2015, 4:23:38 AM (7 years ago)
Author:
Jun Omae
Comment:

Added #11973 to troubleshooting

Legend:

Unmodified
Added
Removed
Modified
  • TracGit

    v22 v23  
    143143* 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.
    144144* 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.
    145 * For Trac < 1.0.6, a repository with many branches makes Trac slow (#11971)
     145* For Trac < 1.0.6, a repository with many branches makes Trac slow (#11971).
    146146* 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.
    147147* 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).
     148* For Trac < 1.0.5, `git` processes can stay open forever like this with bitten-slave (#11973).
     149{{{
     150/usr/bin/git --git-dir=/path/to/git log --pretty=format:%n%H --name-status 324a8d5... --
     151...
     152}}}
    148153
    149154== Known Issues