2013-01-25 22:04:03 by Ryo ONODERA | Files touched by this commit (4) |
Log message:
Update to 3.04
* Update MESSAGE.
Changelog:
* Re-written from scratch, this is gilolite g3.
|
2012-10-31 12:19:55 by Aleksej Saushev | Files touched by this commit (1460) |
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
|
2012-10-03 23:59:10 by Thomas Klausner | Files touched by this commit (2798) |
Log message:
Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.
I hope that's all of them.
|
2012-02-13 18:14:13 by Min Sik Kim | Files touched by this commit (1) |
Log message:
Derive gitolite's PKGNAME from its DISTNAME.
|
2011-11-20 20:11:49 by Ryo ONODERA | Files touched by this commit (7) | |
Log message:
Import gitolite-2.2 as devel/gitolite
Gitolite is an SSH-based gatekeeper providing access control for
a server that hosts many git repositories. Without gitolite, each
developer needing to push to one of the repositories hosted would
need a user account on that server; gitolite lets you do that just
using SSH public keys tied to a single, common, user that hosts
all the repositories.
Gitolite can restrict who can read (clone/fetch) from or write
(push) to a repository, and who can push to what branch or tag -
an important issue in corporate environments. Other features include:
* access control by branch-name or by modified file/directory;
* per-developer "personal namespace" prefixes;
* simple but powerful configuration file syntax (with validation);
* config files (and authority for maintaining them) can be split;
* easy integration with gitweb;
* comprehensive logging;
* easy migration from gitosis.
|