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

remote development optimization

From: Bosnjak Zoran ITWEP1 <Bosnjak_at_iskratel.si>
Date: 2006-01-13 16:43:57 CET

May I copy or move a "working copy" and then use it normaly (as if I
just did a clean checkout)?

Do I need to do run "svn update" or anything else, before use a clone of
working copy?

For example:

$svn checkout repos/proj1 p1
<user1 does not make any changes to p1 after checkout or update>

$cp -a user1/p1 ./p2
$cd p2
$svn switch repos/mybranch
<edit, svn add, svn delete...>
$svn commit

- same procedure as user2

Is this regular procedure?

In my example user1 (virtual), user2 and user3 are on (same) remote
location with slow https connection to the reposotory, but the project
is big. I want to transfer a big chunk of data only once and then share
this data inside the group. May I use "svn update" and local copy

Is there any other "best practice" to replicate server's information for
faster remote access.

Thanks for your help.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 13 17:29:41 2006

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.