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

Re: copying a checkout

From: Delbert D. Franz <iqdotdt_at_sonic.net>
Date: 2005-01-21 19:24:56 CET

Copying a checkout (a working copy) will work fine so long as all the
hidden and readonly files are transfered. The archive (-a) option
on Linux does that. On Windows one has to use drag and drop or
a whole series of options to get a command-line copy to copy
everything.

I have limited outgoing bandwidth from our current server and the
working copies are > 1 GB in size. Thus for two remote computers
I did a zip (making sure flags were set to include read-only and
hidden files) and then burned a CD to send to the remote sites.
These sites were using MS Windows while I use both MS Windows and
Linux with the server on Linux. I have eol-style:native in this
setup. The working copies on the remote computers work fine.

 

    Delbert
On Friday 21 January 2005 06:17 am, Earl A. Killian wrote:
> I have one site with the svn repository, and another site with 3
> machines. I have done a "svn co" on the first machine at the remote
> site and it is still going hours later. So rather doing "svn co" on
> the 2nd machine at the remote site, I want to do on machine1
> rsync -a trunk machine2:
> which will be much faster. However, I don't know if there is any
> per-client information in the .svn directories. Does anyone know if
> this will work?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 21 19:32:17 2005

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

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