[Feature Request] improved gitolite support: negative permissions for protected branches

[wilsoc5]

Negative permissions can be very handy to restrict access to certain tags or branches.
Gitolite documentation refers to it: http://gitolite.com/gitolite/conf.html#what-does-a-rule-look-like

Similarly, option support for "option deny-rules = 1" would be a nice add as well.

[wilsoc5]

It might be useful to also support the @ALL group for the users field in order to restrict read access to a particular repository for any additional users that get added to a project (Explicit permission as opposed to implicit permission).

[dprovorse]

+1 for this. Definitely would be helpful!

[ghost]

+1, this is actually what I need !

[n-rodriguez]

Added in commit : 8f7e433

Example (from Gitolite):

repo    blibl
  RW+                            = redmine_admin
  -     master                   = redmine_developer1 redmine_developer2 redmine_developer3
  -     refs/tags/v[0-9]         = redmine_developer1 redmine_developer2
  RW+   dev/                     = redmine_developer1 redmine_developer2 redmine_developer3
  RW                             = redmine_developer1 redmine_developer2 redmine_developer3
  R                              = redmine_reporter1
  config redminegitolite.projectid = blibl
  config redminegitolite.repositoryid = 
  config redminegitolite.repositorykey = bMs2qj6sPl1ttTZJH5vWJOClIQ2V8ZhwK2d7Szy1CnSDX0EYzE7SuTgAnyrVS7b
  config http.uploadpack = true
  config http.receivepack = true
  config multimailhook.enabled = false
  option mirror.master = mars
  option mirror.slaves = phobos deimos
  option mirror.redirectOK = all