[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: All the .svn directories

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Tue, 4 Mar 2008 22:16:20 +0000

On 04/03/2008, DavidW <dwhite_at_gbcsci.com> wrote:
> Andy Levy <andy.levy@...> writes:
> >
> > That is a common complaint, but SVN was designed this way
> > intentionally. This design allows you to take any directory in your
> > WC, move it somewhere else (thumbdrive), and keep working with it
> > (every directory can be its own self-contained WC).
> Okay, but I didn't think those directories were critical. Aren't they just
> caches of stuff to improve performance? If so, you don't really need them when
> you copy the project elsewhere because they can be re-created.

They are absolutely critical to the operation of the subversion client
library, which is what TSVN uses, so no you can't live without them.
There are plans to redesign the working copy model completely for
Subversion 2.0, using completely separate meta-data, but that is a
long way off.

> > To change it would require a major architectural change to Subversion.
> >
> > Look into SVK if this is really bothering you (it's built on top of
> > SVN); it does keep the metadata outside your working copy, but I don't
> > know if TSVN works with it.

No, TSVN uses the svn client library. SVK uses the svn client-server
protocol to talk to an Subversion server, but has its own working copy
model which is not compatible.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-03-04 23:16:27 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.