James G. Sack (jim) wrote:
Does your situation sound anything like this? (contains reference to a
workaround concept but it's not clear how to implement it)
Ah...yes, I think that's it. Here's a message from further up that
thread which explains it:
http://svn.haxx.se/dev/archive-2008-07/0494.shtml
So there is a workaround but it isn't a very good one as I have to edit
the .svn/config file in every checkout. Or I could just use a different
transport such as http or svnserve. http is appealing because the httpd
does the access control and everything in the repo is owned by one user.
Right now I sometimes have permissions problems because if I check in
code as me it gets owned by me and other people can't overwrite it. One
way to fix that is to have a group and put everyone in it but as I've
learned from dealing with CVS repository permissions (while never
actually using CVS itself) that is a real hassle.
--
Tracy R Reed Read my blog at http://ultraviolet.org
Key fingerprint = D4A8 4860 535C ABF8 BA97 25A6 F4F2 1829 9615 02AD
Non-GPG signed mail gets read only if I can find it among the spam.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
