On 1/1/14, 11:55 AM, Peter Flynn wrote:
Apparently so; and this appears to be new (recent) behaviour. Quite why svn
believes it needs to check the permissions one level above where it was told
to
go is unclear to me, but I'm sure wiser heads have thought this one through.
This is actually
I have a number of svn repositories running under Apache+subversion on
CentOS6/64, with Submin to provide a web GUI to manage them:
server.name/svn/foo
server.name/svn/bar
server.name/svn/blort
etc
All of them are private; all but one of them are single-user (me) so
that I can carry on
On 2013-12-01 15:39, Peter Flynn wrote:
I have a number of svn repositories running under Apache+subversion on
CentOS6/64, with Submin to provide a web GUI to manage them:
server.name/svn/foo
server.name/svn/bar
server.name/svn/blort
etc
All of them are private; all but one of
On 12/01/2013 04:51 PM, olli hauer wrote:
On 2013-12-01 15:39, Peter Flynn wrote:
I have a number of svn repositories running under Apache+subversion on
CentOS6/64, with Submin to provide a web GUI to manage them:
server.name/svn/foo
server.name/svn/bar
server.name/svn/blort
etc
Hi Peter
From: Peter Flynn
Sent: Monday, 2 December 2013 1:40 AM
I have a number of svn repositories running under
Apache+subversion on CentOS6/64, with Submin to provide a web
GUI to manage them:
server.name/svn/foo
server.name/svn/bar
server.name/svn/blort
etc
All of
On 12/1/13 6:39 AM, Peter Flynn wrote:
I have a number of svn repositories running under Apache+subversion on
CentOS6/64, with Submin to provide a web GUI to manage them:
server.name/svn/foo
server.name/svn/bar
server.name/svn/blort
etc
All of them are private; all but one of them
