Differences

This shows you the differences between two versions of the page.

--- pld-gitolite [2012-04-01 10:46] – [Email notifications] draenog
+++ pld-gitolite [2016-03-21 10:20] (current) – [Authentication] glen
@@ Line 18: / Line 18: @@
 Authentication is based on ssh keys. People whose keys are in SSH-keys in PLD repository should have access.
+[[howto-git#rw_access_ussing_ssh_public_keys|Manage your keys]]
+===== Changes to Developer =====
+Changes to developer can be seen from [[cvs2git]] page.
 ===== Access control=====
 ==== Assumptions: ====
@@ Line 52: / Line 56: @@
 ===== New package creation =====
-In upstream version of gitolite, new package is created by cloning of no existing repo (if the access rules allow for it). However I think that it is too error prone. So [[https://github.com/draenog/gitolite|gitolite was forked]] and an option to disable creation of wildcard repositories was added. Instead an [[http://sitaramc.github.com/gitolite/doc/admin-defined-commands.html|admin defined command]] was created for this task:
+In upstream version of gitolite, new package is created by cloning of no existing repo (if the access rules allow for it). However I think that it is too error prone. So [[https://github.com/draenog/gitolite|gitolite was forked]] and an option to disable creation of wildcard repositories was added. Instead an [[http://sitaramc.github.com/gitolite/ADCs.html|admin defined command]] was created for this task:
   ssh draenog@carme.pld-linux.org create <new_repo>
 =====Package deletion=====
-People with write access to gitolite-admin repository can use [[http://sitaramc.github.com/gitolite/doc/admin-defined-commands.html|admin defined command]] to move obsoleted packages to attic space:
+People with write access to gitolite-admin repository can use [[http://sitaramc.github.com/gitolite/ADCs.html|admin defined command]] to move obsoleted packages to attic space:
   ssh draenog@carme.pld-linux.org  trash <repo>
 =====Restrictions on committed files====
 It is possible to prevent the commits of large files or archives. Currently every file must pass the following tests:
-  * its size is smaller then 1 MB or its name matches one of patterns: *.spec, *.patch, *.diff
+  * its size is smaller then 200kb or it is a text file smaller then 2Mb or its name matches one of patterns: *.spec, *.patch, *.diff
   * it is not a zip or compressed file
   * it is not a tar archive