Re: proposing svn write for public repos

Hi,

On Mon, Jul 02, 2007 at 01:58:14PM +0200, Tobias Hintze wrote:
> and personal repositories like:
> 
> rock-linux/trunk/package/blindcoder/
> rock-linux/trunk/package/clifford/
> rock-linux/trunk/package/daja77/
> rock-linux/trunk/package/stefanp/
> rock-linux/trunk/package/teha/
> (alphabetical order)
> 
> personal repositories should be writable by the "personal owner", the
> "public" repo should be writable by a set of developers (blindy, daja,
> stf, myself)

there are 36 "CORE" packages in this repositories - most of them in
'public'. I propose that we move them to another repository first..

> i know - this allows creation of some preconfig.in files and MIGHT still
> allow people to do bastardious things... i'm willing to take this risk.
> (we should restrict write access to people who have proven to be not
> bastardious in the last years)
> and if you insist - we can still check for such dangerous files in some
> svn-hook and disallow the transaction.

would you write this hook?

The hook should also check for the right commit message format and
information so there is no conflict with fixauthor.spl (the SPL script
which is parsing the commit messages and setting the author revision
property according to it).

This is very important! There is no history for revision properties, so
there also is no way to detect and probably rollback errornous automatic
updates of this property.

> everything else should go through submaster.

fine with me since non-CORE patches are simply passed thru atm without real
testing anyways..

yours,
 - clifford

-- 
perl -le '$_=1;(1x$_)!~/^(11+)\1+$/&&print${_}while$_++<1000'|fmt