Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

docs and .gitattributes hadn't been updated for the change in hooks dir

  • Loading branch information...
commit b3945d44c9c0f70054aebb3edc7b488c0544210b 1 parent 4b7d144
Sitaram Chamarty authored March 10, 2010
7  .gitattributes
... ...
@@ -1,3 +1,4 @@
1  
-conf/*          crlf=input
2  
-src/*           crlf=input
3  
-src/hooks/*     crlf=input
  1
+conf/*                  crlf=input
  2
+src/*                   crlf=input
  3
+hooks/common/*          crlf=input
  4
+hooks/gitolite-admin/*  crlf=input
4  conf/example.conf
@@ -253,8 +253,8 @@ gitolite "Sitaram Chamarty" = "fast, secure, access control for git in a corpora
253 253
 # syntax:
254 254
 #   config sectionname.keyname = [optional value_string]
255 255
 
256  
-# example usage: if you placed a hook in src/hooks that requires configuration
257  
-# information that is specific to each repo, you could do this:
  256
+# example usage: if you placed a hook in hooks/common that requires
  257
+# configuration information that is specific to each repo, you could do this:
258 258
 
259 259
 repo gitolite
260 260
     config hooks.mailinglist = gitolite-commits@example.tld
10  doc/2-admin.mkd
Source Rendered
@@ -99,15 +99,15 @@ for the special usernames or remove the description line.
99 99
 #### custom hooks
100 100
 
101 101
 If you want to put in your own, custom, hooks every time a new repo is created
102  
-by gitolite, put a **tested** hook script in `src/hooks`.  As distributed, the
103  
-only file there is the `update` hook, but everything (*everything*) in that
104  
-directory will get copied to the `hooks/` subdirectory of every *new* repo
105  
-created.
  102
+by gitolite, put a **tested** hook script in `hooks/common` of your gitolite
  103
+clone before running easy-install.  As distributed, there are only two files
  104
+there, but everything (*everything*) in that directory will get copied to the
  105
+`hooks/` subdirectory of every *new* repo created.
106 106
 
107 107
 In order to push a new or updated hook script to *existing* repos as well,
108 108
 just run easy install once again; it'll do it to existing repos also.
109 109
 
110  
-**VERY IMPORTANT SECURITY NOTE:  the `update` hook in `src/hooks` is what
  110
+**VERY IMPORTANT SECURITY NOTE:  the `update` hook in `hooks/common` is what
111 111
 implements all the branch-level permissions in gitolite.  If you fiddle with
112 112
 the hooks directory, please make sure you do not mess with this file
113 113
 accidentally, or all your fancy per-branch permissions will stop working.**

0 notes on commit b3945d4

Please sign in to comment.
Something went wrong with that request. Please try again.