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

Re: .SVN folder question

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-07-19 18:38:56 CEST

"Sindbad the Seafarer" <sindbad.the.seafarer@gmx.net> writes:

> > 1. Try 'svn export'. It's like a checkout, but produces an
> > unversioned tree (i.e. no .svn/ folders)
> This would be even worse I suppose: it does not keep the file dates
> from the working copy but in truth re-creates the files at the
> destination. Thus all files are be new and uploaded to the
> webserver. While some searchengines are said to love files with
> new file date it would cause daily uploads of 60+ MB, perhaps even
> far more than just including the .svn folders. For that reason I
> already did not import anything to the newly created repository but
> only made a trunk folder and checked this practically empty repos
> out. Then copied the existing files in the file manager to that bare
> bones working copy and added them to the repos from there. This
> way all file dates/attributes remained unchanged and I can continue
> synchronizing with the web server as before (.svn folders aside).

Why not do what most of us do? Keep the working copy on the web
server, and make it the "live" tree served to the world. Just 'svn
update' the live copy from time to time, rather than "reuploading" a
whole new tree to the server.

In fact, I even have a post-commit hook in my repository which
automatically updates my live working copy.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 19 18:41:27 2003

This is an archived mail posted to the Subversion Dev mailing list.

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