On Fri, Jul 19, 2013 at 1:22 PM, Z W <mpc8250_at_gmail.com> wrote:
> Thanks for responding with your detailed answers.
> I would take your suggestion to copy Z branch into Y and then merge Y into
> I'm not sure what externals are for.
Externals are for where you want a component to appear within one or
more other projects - like library code, and you want the ability to
mange the release/versioning separately. You put the component in a
separate repository or at a separate project level directory in the
same repository, probably with its own trunk/branches/tags layout, and
use the svn:externals to pull in the revision you want of that
component in each of the other projects that need it. Typically you
would test/tag the component revisions before using them - and point
the externals to tags, but additional development can proceed
concurrently without affecting the consuming projects until they
adjust their external references to a new tag location.
> Another question:
> Under what circumstance would one use "svn switch". I understand what it can
> do but I still don't see clearly its purpose.
svn switch updates your checked-out workspace to match the revision at
a different url path. It's the way to move between working on
trunk/branch/tag versions of things.
Received on 2013-07-19 20:45:29 CEST