RE: performance enhancement by working copy svn server

> > I think the general consensus is that the default svn behavior will
> > not change; 'svn edit' will be an optional mode of working,
> for those
> > who want or need the speed tradeoff.
>
> I figured that from later postings in the thread, but it's
> good to see it spelled out clear.

Correct, the default behavior will not change - 'svn edit' remains optional.

However, the WC backend is likely to change. Consolidating all the .svn subdirs into a single file, or into a single dir.

<anecdote>
For me in particular, this will be very welcome. I have a badly-behaved tool (from Cadence) and this is its behavior:
        The Cadence tool assumes it owns a whole directory that you're working on.
        It goes in, modifies all the stuff it cares to modify...
        It finds the ".svn" directory, deletes it, and creates a ".svn" file containing only a Space char.
        And then I'm unhappy.
</anecdote>

This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at netadmin_at_patni.com and delete this mail.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-17 22:11:12 CEST