From dc62d69848a971625b2ab545aceda388cfaa11ee Mon Sep 17 00:00:00 2001 From: Sitaram Chamarty Date: Mon, 4 Oct 2010 19:28:33 +0530 Subject: [PATCH] progit doc... thanks to tsgarp for making me think about adding this caution --- doc/progit-article.mkd | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/progit-article.mkd b/doc/progit-article.mkd index ce967f8..da016d3 100644 --- a/doc/progit-article.mkd +++ b/doc/progit-article.mkd @@ -1,5 +1,9 @@ ## Gitolite ## +Note: the latest copy of this section of the ProGit book is always available within the [gitolite documentation][gldpg]. The author would also like to humbly state that, while this section is accurate, and *can* (and often *has*) been used to install gitolite without reading any other documentation, it is of necessity not complete, and cannot completely replace the enormous amount of documentation that gitolite comes with. + +[gldpg]: http://github.com/sitaramc/gitolite/blob/pu/doc/progit-article.mkd + Git has started to become very popular in corporate environments, which tend to have some additional requirements in terms of access control. Gitolite was originally created to help with those requirements, but it turns out that it's equally useful in the open source world: the Fedora Project controls access to their package management repositories (over 10,000 of them!) using gitolite, and this is probably the largest gitolite installation anywhere too. Gitolite allows you to specify permissions not just by repository, but also by branch or tag names within each repository. That is, you can specify that certain people (or groups of people) can only push certain "refs" (branches or tags) but not others.