deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
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.
185 commits 6 branches 50 tags 2.8 MiB
Perl 88.8%
Shell 10.3%
Public Key 0.8%
Raku 0.1%
Find a file
Sitaram Chamarty 581e79d745 logging die and warn messages 
- change a few important die()s to _die()s
  - setup SIGs for both die and warn so any others will get caught
2012-04-18 06:23:21 +05:30
doc yaaay! http is finally done! 2012-04-15 21:14:56 +05:30
src logging die and warn messages 2012-04-18 06:23:21 +05:30
t yaaay! http is finally done! 2012-04-15 21:14:56 +05:30
check-g2-compat (some minor changes) 2012-04-05 21:31:59 +05:30
convert-gitosis-conf (mostly) doc changes 2012-04-10 15:41:32 +05:30
dot.pl Q: all doc stuff 2012-03-24 18:22:11 +05:30
install supporting DOS and fake Unix... 2012-04-06 21:13:56 +05:30
README.mkd new README, in preparation for rolling the new release into "master" 2012-04-05 19:19:36 +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]).