Re: svn edit

>>>>> Blair Zajac <blair_at_orcaware.com>:

> Ben Collins-Sussman wrote:

>> ... It's basically imitating perforce: the entire working copy is
>> read-only. When you want to edit a file, you run 'svn edit file',
>> which makes the file read-write and registers this fact in sqlite.

> Have we decided that this is something we really want?

I'm an unwilling and unhappy perforce user, and I don't want to see this
behaviour in perforce as well.

> It does sound very annoying and restrictive.

It is very annoying for code versioning, especially when IDE tools start
changing files without doing "p4 edit".

Things can become very messy (IDEs of experience: eclipse and Visual
Studio. Both are bad, but VS and perforce are the worst).

It is very restrictive for one of my use cases, which is version control
of my unix/linux home control. There I empathically _don't_ want this.

For this use cse I like the fact that SVN stores the actual access on
the files, and can recreate that.

Bad, bad, bad! Please don't do it!

- Steinar

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-26 13:53:48 CET