[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: Paul Hammant <paul_at_hammant.org>
Date: Fri, 21 Jul 2017 05:00:32 -0400

>
>
> 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).

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.

Sure, it's only read-only bit and can be flipped by anyone who can launch
WindowsExplorer and pop a properties tab for the file, etc. That's worth
mentioning because the time honored provision of corporate files over a
network share comes with an ability to lock the read-only bit for files.
That said the end user could copy those files to their C: drive.

- Paul
Received on 2017-07-21 11:00:40 CEST

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