Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: Proposal: mod_authz_svn to get an option to inform clients that
 resource 'cannot be written to'
To: dev@subversion.apache.org
References: <CA+298UiZ+-bvaHHZXfwfa7u-nEWoqVP5LTYQ1nmkehZZ3BGmiQ@mail.gmail.com>
 <CA+298UisNzb=zC+3xNDPXCC5c1surAbSybKSuOXUm4Sh6Q5nhA@mail.gmail.com>
 <CAEyhmwYZ18ub=mA1EMCMBwLT8-e2ErSgNe=xHLf_szzZ1Sa=9A@mail.gmail.com>
 <CA+298Uge=1ZOSA8Q_rJZyurTUexQxDw47y1rvD0cJ5Ae_FK8RA@mail.gmail.com>
From: =?UTF-8?Q?Branko_=c4=8cibej?= <brane@apache.org>
Organization: The Apache Software Foundation
Message-ID: <f2d65df8-c817-2212-25b5-63205a1512fc@apache.org>
Date: Fri, 21 Jul 2017 11:14:12 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CA+298Uge=1ZOSA8Q_rJZyurTUexQxDw47y1rvD0cJ5Ae_FK8RA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
archived-at: Fri, 21 Jul 2017 09:14:19 -0000

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