RE: performance enhancement by working copy svn server

At 3:00 PM -0400 4/10/08, Harvey, Edward wrote:
> > The whole working copy would have
>> read-only permissions set by default; 'svn edit' would make
>> a file read-write.
>
>Actually, I think this sounds very reasonable (as an option; I do
>respect the need for people to continue working the way they always
>have before). It's a quick & dirty, easy simple technique to nearly
>eliminate the whole problem. No architecture dependent (well,
>minimal) code, which still (usually) creates the ability for the svn
>client to monitor all the file edits.

Let me add this observation: You might also need to have directories
to be marked as read-only by default. There are some commands which
will alter a file by making changes to a copy of it, and them removing
the old file by moving in the new file. I've had .svn working copies
corrupted by this, for instance, even though the *files* in the .svn
directory are permitted read-only to me.

-- 
Garance Alistair Drosehn            =   gad_at_gilead.netel.rpi.edu
Senior Systems Programmer           or  gad_at_freebsd.org
Rensselaer Polytechnic Institute    or  drosih_at_rpi.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org