Ideas for tracking Authz changes in a repo

2017-11-28 Thread Paul Hammant
One thing I need to be able to do in the near term is track when authz settings change for a user (or groups). It'd be great if Svn had the authz file (optionally) under source control. I'd be happy with 1) a robot user performs a *copy* of the file from its canonical location and automatic commi

Re: Ideas for tracking Authz changes in a repo

2017-11-28 Thread Mark Phippard
On Tue, Nov 28, 2017 at 8:55 AM, Paul Hammant wrote: > One thing I need to be able to do in the near term is track when authz > settings change for a user (or groups). > > It'd be great if Svn had the authz file (optionally) under source control. > I'd be happy with > > That feature was added in

Re: Ideas for tracking Authz changes in a repo

2017-11-29 Thread Paul Hammant
Thanks for this Marc. I'll go ahead and play with it to learn it capabilities and (hopefully few) snags. - Paul

Re: Ideas for tracking Authz changes in a repo

2017-11-29 Thread Paul Hammant
s/Marc/Mark/ sorry ... I've been dealing with a fellow with the other spelling today in work.

Re: Ideas for tracking Authz changes in a repo

2017-12-04 Thread Stefan Fuhrmann
On 29.11.2017 18:40, Paul Hammant wrote: Thanks for this Marc. I'll go ahead and play with it to learn it capabilities and (hopefully few) snags. In 1.10 and for svn:// since 1.9, in-repository authz can be a lot faster than file-based authz. The reason is that repositories provide O(1) update