Josef Wolf <jw@raven.inka.de> writes:
> The question is whether I should post it directly to the list (about
> 1300 lines) or should I rather mail it to a specific person with
> commit permissions who will commit it into the repository?
Post directly to the list, or post a URL where people can get the
code. It should be reviewed before being put in tools/, if possible.
> Features:
> - You can create new repositories. When creating a new repository, you
> can choose one of the (previosly defined) templates for this new repos.
> The template defines any initial files, directories, property settings
> and pre-commit/post-commit definitions (such as access permissions
> and commit-email).
> - You can add/delete users to the svn-passwd and change their passwords.
> Every user can change its own password, of course.
> - You can define which users have access (read/write) and which ones have
> administration permissions to which repositories.
> - The CGI registers itself as [pre|post]-commit-hook. This way it is able
> to implement access restrictions, send commit-emails and do
> database-backups after every commit.
> - You can browse/edit commit-logs in a (IMHO) more convinient way than
> tweak-log.cgi does.
> - You can quickly browse which changes any commit does to the repository.
> - It is already prepared for support of different languages (currently
> english and german).
Sounds nice!
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jan 5 18:34:51 2003