On 09/03/16 16:44, Niemann, Hartmut wrote:
Hi!
I learned that finer-as-per-repository-grained read access is rather
"expensive" in terms of server load
because rights have to be checked for each file updated.
So it would be best that you have separate repositories for separate "read"
user gr
hi everybody,
I realize this certainly is somewhere in books but I'm
hoping few experts would not mind sharing their
thoughts/recommendations on how to...
set up svn structure where interface to it is only http and
flexibility + ability to finely grain user access is the key
objective - thu
catch their
creation in a post-commit script, and regenerate your
access file?
Eric.
On Thu, Feb 26, 2015 at 8:47 AM, lejeczek
mailto:pelj...@yahoo.co.uk>> wrote:
hi everybody
as a novice I understand I'm looking for shortcuts,
probably being not the first one I&
hi everybody
as a novice I understand I'm looking for shortcuts, probably
being not the first one I'd have this question:
does Subversion implement any variables in it's configuration?
first case to exercise this scenario would be AuthzSVNAccessFile
could one have
[REPO_NAME:/_$user]
_$user =
hi users
I don't suppose this would be possible without hacking the
code, right?
Reason I'm asking is simplicity and clearness in the message.
eg. is when an attempt to lock fails for file is already
locked by other user
why bother users with the path to file on a remote resource?
they usually
