{"thread":{"id":"22587","subject":"[Announce] gitolite 1.0","startedAt":"2010-02-09T13:15:26Z","lastAt":"2010-02-09T13:15:26Z","messageCount":1,"participants":["Sitaram Chamarty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"134036","messageId":"2e24e5b91002090515o356c53baib1f5f750e0d67dba@mail.gmail.com","threadId":"22587","inReplyTo":null,"subject":"[Announce] gitolite 1.0","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2010-02-09T13:15:26Z","receivedAt":"2010-02-09T13:15:26Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"Gitolite is an ssh-based access control tool for using git in a typical\n\"corporate\" environment.  The original goals were very simple:\nread/write/rewind access control at the git branch level, the ability to\ninstall on any Unix, no need for root access, and no need for additional\nsoftware (other than git and perl).\n\nThere is plenty of documentation included with the source, because by\nnow it has acquired a lot of features not originally planned.\n\nI now consider gitolite to be at 1.0, and this note summarises the\nfeatures added since the last email to the list [1] about gitolite.\nPlease see README.mkd and doc/3-faq-tips-etc.mkd for *all* the details\nif you are completely new to gitolite.\n\n  * Install/upgrade can now be done even from the bash that comes with\n    msysgit.  This means pretty much anyone can quickly and easily\n    install gitolite on any Unix server.\n\n  * You can specify an \"owner\" and a \"description\" for gitweb to\n    display.  The syntax is very simple, here's an example:\n\n        gitolite \"Sitaram Chamarty\" = \"fast, secure, access control for git\"\n\n  * You can include any site-specific (custom) hooks that you want to\n    propagate to any repo created by gitolite.\n\n  * The \"deny access\" feature can be very useful sometimes; an example\n    that shows how only bob may push version tags would look like this:\n\n        @devs                       =   alice bob charlie\n\n        RW      refs/tags/v[0-9]    =   bob\n        -       refs/tags/v[0-9]    =   @devs\n        RW      refs/tags/          =   @devs\n\n    More details can be found in the documentation.\n\n  * Gitolite can now let you specify restrictions based on file/dir\n    names (for example, restrict who can push changes that touch some\n    file or directory).\n\n    My initial response to this request was that this is better done by\n    the social mechanisms of the project team, and I do not believe this\n    feature is really necessary in a well-run project.\n\n    However, people coming from other VCSs seem to make this a sticking\n    point at work, so I added it anyway, if only to see how far I could\n    stretch gitolite's config file while keeping its simplicity intact\n    :-)\n\n----\n\nI'm often on #git, subject to my living in UTC+0530 time, and email is\nalso welcome (sitaramc <at> gmail.com is preferred, but sitaram.chamarty\n<at> tcs.com may get my attention quicker).  Feel free to contact me\nwith questions or feedback.\n\n-- \nSitaram\n\n[1]: http://article.gmane.org/gmane.comp.version-control.git/131834\n\n\n-- \nSitaram\n"}]}