[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Proposal: mod_authz_svn to get an option to inform clients that resource 'cannot be written to'

From: Branko ─îibej <brane_at_apache.org>
Date: Fri, 21 Jul 2017 11:14:12 +0200

On 21.07.2017 11:00, Paul Hammant wrote:
>
>
> What is the story? How is this going to help Subversion users?
>
> The idea sounds interesting. However, I'm not sure how it will help
> the users. I don't mind whether I have Read Only or Read / Write
> access to an FTP resource or another kind of remote data. I just know
> whether I have access to the resource or not. IMO, this is a
> communication problem and it's not what SVN has to solve.
>
>
> It will help the owners of subversion repos preventing files from
> being overwritten that they do not want to be overwritten. e.g.
> Company's Word template (.DOT files).

Use the svn:needs-lock property.

> It will help subversion end-users not upset the owners of repositories
> by changing files (and committing them back) that there are not
> supposed to.

Use access control.

-- Brane
Received on 2017-07-21 11:14:18 CEST

This is an archived mail posted to the Subversion Dev mailing list.