Sitaram Chamarty 089f0f9d9e on removing a repo... ... Not following through on instructions to remove a repo, per [1], is not sufficient. Even if you did just the first step, the repo should no longer be accessible. See [2] for discussion. As a bonus, we get rid of one pesky warning that always confused people. (In hindsight -- this confusion itself should have been a warning that something is wrong and needed fixing!) [1]: http://sitaramc.github.com/gitolite/repos.html [2]: http://groups.google.com/group/gitolite/browse_thread/thread/a3d4c3e917056abb		2012-12-31 06:23:28 +05:30
..
Conf	on removing a repo...	2012-12-31 06:23:28 +05:30
Hooks	GL_BINDIR2 becomes LOCAL_CODE, allows hook propagation also...	2012-06-14 19:22:12 +05:30
Test	a few minor changes	2012-12-04 05:43:48 +05:30
Triggers	new features relating to creating wild repos:	2012-11-22 20:50:20 +05:30
Common.pm	add more detail to error message	2012-12-14 07:58:14 +05:30
Conf.pm	PRE_ and POST_CREATE should work for normal repos also	2012-05-25 12:47:12 +05:30
Easy.pm	(minor docfix) add info on using Easy.pm from elsewhere	2012-09-19 17:47:12 +05:30
Rc.pm	Uggh; horrible inner loop screwing up all performance :-(	2012-11-14 15:43:57 +05:30
Setup.pm	(minor) improve SNR of some error messages :)	2012-06-17 09:31:38 +05:30
Test.pm	Bailout tests unless envvar $GITOLITE_TEST is 'y'	2012-08-10 11:31:48 +05:30
Triggers.pm	supporting DOS and fake Unix...	2012-04-06 21:13:56 +05:30