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

Re: Help or suggestions on porting to subversion

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Thu, 11 Nov 2010 13:31:37 -0600

On 11/10/2010 3:05 PM, San Martino wrote:
> Hello Ryan,
> Of course the cleanest way is to checkout the whole trunk/ and tag the
> trunk each time.
> A single checkout of the whole / directory is tens of GB over a
> network (non-LAN), multiply this for all the deveopers.

But this should only have to happen once per workspace needed - and you
could even copy the initial workspace if you need multiple copies at a
remote location. Or ship them a workspace on a USB drive. From then
on, only differences should be transferred.

> The solution does not scale well even if checkout with --depth is
> disabled. Furthermore tagging the whole trunk each time would be make
> the concept it is for pointless.

Tagging really just gets you a human-friendly name, at least in the
conventional use where the tag is a copy from a branch or trunk
revision. There's no difference in what you can do with a tag url than
the url plus revision that was the source of the copy. And there should
also not be much if any difference in efficiency if you 'svn switch'
your working copy there. It's just easier to document your processes
when you can make up the tag names you should use for certain steps.

   Les Mikesell
Received on 2010-11-11 20:32:19 CET

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.