Re: Locking functional spec: read-only WC

Justin Erenkrantz wrote:
> Greg Hudson's directory lock message implicitly brought up the issue
> with the working copy being set to read-only.
> In closing, I think the tool should prevent me from checking in my
> changes without the lock, but it shouldn't obstruct me from modifying my
> local copy: I own it and should do whatever I want to it. I look back
> at how much I hated RCS's behavior and I don't want to go back to that.
> I think the WC files should be read-write at all times and throw
> messages at the client when they try to commit to something that has an
> active lock. But, having read-only WC files seems like it's going to
> suck. -- justin

I think that the opposing views on read-onlyness of locked files are both valid:-(

I would want to know a file was locked before editing it because I never work disconnected.

Therefore I would like to propose either a client configuration option or a command line option to
svn checkout/update to turn off making locked files read-only.

E.g.:

svn checkout http://... wcname --locked-files-not-readonly

I am sure someone can come up with a better switch name than that:-)

-- 
Martin Tomes
echo 'martin at tomes x org x uk'\
  | sed -e 's/ x /\./g' -e 's/ at /@/'
The Subversion Wiki is at http://www.subversionary.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org