Jan Keirse wrote: > Setting all that up shouldn't take very long.
Yeah, for one site, but this would be like num_of_sites * num_of_people = ALOT. :) > If you still don't want to do that I think your best bet would be to do > everything related to subversion on the server, maintain the working copy > on the server, do all commits from there. You can still access the working > copy from Samba to do the actual coding, just don't commit anything from > windows. Yeah, this is also a no-op as users (even developers) can't find their way around the command line SVN client, so I'd be the one doing all the commits, too much bus factor. OK, I did some testing and it seems there isn't a good way to get this working (or am I mistaken)? This means I should implement the old setup (which I wanted to avoid): - forcing user and group via Samba - changing the ownership of the files on the server to that user:group combo This leaves much to be desired in the flexibility, but as Subversion is changing the permissions (even through Samba), can't seem to do anything better. Thanks, -- Dado
