Hosting git repositories -- Gitolite allows you to setup git hosting on a central server, with very fine-grained access control and many (many!) more powerful features.
 
 
 
 
Go to file
Sitaram Chamarty e1c7e546aa cpu-time command -> CpuTime trigger module...
...now that triggers are not restricted to external programs and can be
perl code called by gitolite-shell (thus in the same PID), there's no
need to compute and pass along the times() array.

This also changes the arguments to POST_GIT; they're now the same as
PRE_GIT's.
2012-04-06 17:26:27 +05:30
doc cpu-time command -> CpuTime trigger module... 2012-04-06 17:26:27 +05:30
src cpu-time command -> CpuTime trigger module... 2012-04-06 17:26:27 +05:30
t cpu-time command -> CpuTime trigger module... 2012-04-06 17:26:27 +05:30
README.mkd new README, in preparation for rolling the new release into "master" 2012-04-05 19:19:36 +05:30
check-g2-compat (some minor changes) 2012-04-05 21:31:59 +05:30
dot.pl Q: all doc stuff 2012-03-24 18:22:11 +05:30
install put the VERSION file in the right place 2012-04-02 13:18:30 +05:30

README.mkd

Gitolite README

Github users: please read the "wiki" link at the top of the page before submitting issues or pull requests.


If you're reading this on the main gitolite page on github, several IMPORTANT CHANGES have happened to gitolite:

  1. A competely re-written version of gitolite has been pushed to the "master" branch, and is now the actively maintained and supported software. Do NOT try to merge this with your old "master" branch!

  2. Versions v2.x is on branch "g2". It will be supported for security issues and serious bugs in core functionality, but not for anything less critical. Versions v1.x are completely unsupported now.

If you're an existing (v1.x, v2.x) gitolite user please spend some time with the documentation for the new version before upgrading. The main page leads to quick install as well as several other useful starting points. The table of contents is a much more meaningfully ordered/structured list of links (instead of putting them in alphabetical order of the filename, like in g2!)


License information for code and documentation is at the end of doc/index.mkd (or you can read it online [here][license]).