| non port: devel/gitolite/files/pkg-message.in |
|
SVNWeb
|
Number of commits found: 7 |
|
Wed, 24 Mar 2021
|
[ 11:56 grembo  ]  
Fix filename in pkg-message
Not worth bumping the revision for.
PR: 254480
Approved by: mat (maintainer)
|
|
Wed, 19 Jun 2019
|
[ 15:20 mat ]
Update the rest of my ports to UCL pkg-message.
|
|
Sun, 5 Aug 2012
|
[ 19:36 swills ]
- Update to 3.04
PR: ports/170394
Submitted by: milki <milki@rescomp.berkeley.edu>
|
|
Thu, 31 May 2012
|
[ 19:14 sylvio ]
- Update to 3.0.3
PR: ports/168378
Submitted by: Milki <milki@rescomp.berkeley.edu> (maintainer)
|
|
Tue, 8 May 2012
|
[ 18:02 crees ]
Correct pkg-message instructions on providing gitolite
Submitted by: maintainer via email
|
|
Mon, 7 May 2012
|
[ 16:52 crees ]
- Update to 3.01
- Register CONFLICTS with gitolite2 legacy port
PR: ports/167440
Submitted by: milki <milki@rescomp.berkeley.edu> (maintainer)
|
|
Fri, 29 Jul 2011
|
[ 22:16 tdb ]
- Add new port gitolite:
Gitolite is an access control layer on top of git, which allows access control
down to the branch level, including specifying who can and cannot rewind a
given branch.
Gitolite lets you use a single user on a server to host many git repositories
and provide access to many developers, without having to give them real
userids on or shell access to the server. Authentication is most commonly done
using sshd, but you can also use httpd if you prefer.
Gitolite can restrict who can read from (clone/fetch) or write to (push) a
repository. It can also restrict who can push to what branch or tag, which is
very important in a corporate environment.
WWW: https://github.com/sitaramc/gitolite
PR: ports/159260
Submitted by: milki <milki at rescomp.berkeley.edu>
|
Number of commits found: 7 |
As an Amazon Associate I earn from qualifying purchases.