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

Re: Client cache centralize vs distributed

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Wed, 17 Dec 2008 10:10:06 +0000

2008/12/17 <tuant20_at_gmail.com>:
> Hello guys,
>
> First of all, sorry if this post is out there some where I didn't know or I couldn't find, in this case please point me to the right place.
>
> Here is the issue:
> I have a working dir with tree of working files. Then I upload my working dir to my web server and the .svn folder in the working dir and its sub-folder has been uploaded along with the working dir. I would not like it that way, what I intended to upload is just my working dir without the .svn things.
> So I wonder why we don't centralize the .svn things to i.e just 1 folder at the first place of the working dir instead of distributed over the tree of the working dir?
>
> Any reply would be appreciated.
>
> Regards,
> Tuan Nguyen

To send the data to your web server you need to use Export, which
copies the data without .svn metadata folders.

The working copy structure is defined by the subversion project,
TortoiseSVN just uses the standard libraries from Subversion so you
would have to ask that question on the Subversion mailing lists.
Having said that I believe svn 1.7 will include a completely
re-written working copy model which may use a centralised database for
the metadata.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=985625
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2008-12-17 11:10:20 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.