| Commit History - (may be incomplete: see SVNWeb link above for full details) |
| Date | By | Description |
24 Apr 2013 19:18:21
  3.5.1,1
|
swills  |
- Update master site
PR: ports/177430
Submitted by: milki <milki@rescomp.berkeley.edu> (maintainer) |
24 Apr 2013 17:54:06
3.5.1,1
|
swills |
- Update to 3.5.1
PR: ports/177430
Submitted by: milki <milki@rescomp.berkeley.edu> (maintainer) |
14 Mar 2013 11:31:58
3.4,1
|
miwi |
- Update to 3.4
PR: 176789
Submitted by: William Grzybowski <william88@gmail.com>
Approved by: naintainer |
17 Feb 2013 20:08:30
3.3,1
|
swills |
- Update to 3.3,1
PR: ports/175727
Submitted by: milki <milki@rescomp.berkeley.edu> (maintainer) |
13 Jan 2013 20:40:33
3.2,1
|
swills |
- Update to 3.2
Changes:
https://github.com/sitaramc/gitolite/blob/5f9789ed8ee519a5987e8fede7f3e65001f4f9c0/CHANGELOG
https://github.com/sitaramc/gitolite/compare/v3.1...v3.2
PR: ports/175243
Submitted by: milki <milki@rescomp.berkeley.edu> (maintainer) |
11 Oct 2012 01:40:59
3.1,1
|
swills |
- Update devel/gitolite to 3.1
- Document security issue in devel/gitolite
PR: ports/172565
Submitted by: milki <milki@rescomp.berkeley.edu> (maintainer)
Reviewed by: eadler
Security: f94befcd-1289-11e2-a25e-525400272390
Feature safe: yes |
05 Aug 2012 19:36:47
3.04
 |
swills |
- Update to 3.04
PR: ports/170394
Submitted by: milki <milki@rescomp.berkeley.edu> |
31 May 2012 19:14:04
3.03
|
sylvio |
- Update to 3.0.3
PR: ports/168378
Submitted by: Milki <milki@rescomp.berkeley.edu> (maintainer) |
08 May 2012 18:02:15
3.01_1
|
crees |
Correct pkg-message instructions on providing gitolite
Submitted by: maintainer via email |
07 May 2012 16:52:01
3.01
|
crees |
- Update to 3.01
- Register CONFLICTS with gitolite2 legacy port
PR: ports/167440
Submitted by: milki <milki@rescomp.berkeley.edu> (maintainer) |
17 Feb 2012 11:50:50
2.3
|
culot |
- Update to 2.3
Changes: https://raw.github.com/sitaramc/gitolite/pu/doc/CHANGELOG
PR: ports/165222
Submitted by: milki <milki@rescomp.berkeley.edu> (maintainer) |
12 Feb 2012 19:55:42
2.2.1
|
jgh |
- Update to 2.2.1
PR: ports/165022
Submitted by: maintainer, milki at rescomp.berkeley.edu |
06 Feb 2012 09:15:06
2.2
|
tdb |
- Update to 2.2
Changes:
https://github.com/sitaramc/gitolite/blob/pu/doc/CHANGELOG
https://github.com/sitaramc/gitolite/compare/v2.1...v2.2
PR: ports/164809
Submitted by: milki <milki@rescomp.berkeley.edu> (maintainer) |
30 Sep 2011 11:39:37
2.1
|
tdb |
- Update to 2.1
Changes:
https://groups.google.com/d/topic/gitolite/CzL4g1vuqbY/discussion
https://github.com/sitaramc/gitolite/compare/v2.0.3...v2.1
PR: ports/161147
Submitted by: milki <milki@rescomp.berkeley.edu> (maintainer) |
24 Sep 2011 11:16:01
2.0.3
|
dhn |
- Update to 2.0.3
PR: ports/160940
Submitted by: milki <milki@rescomp.berkeley.edu> (maintainer) |
29 Jul 2011 22:16:45
2.0.2
|
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> |
If you buy from Amazon USA, please support us by using this link.
