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

svn:externals - process question

From: C M <cmanalyst66_at_gmail.com>
Date: Thu, 31 Jan 2013 11:53:43 -0600


My question is more process related with using svn:externals. In my
testing, it seems that the svn:externals links are bi-directional. Changes
are instantly propagated via the magic of svn:externals.

1. How do users preserve the integrity of a tag (which was created off a
branch which had svn:externals)?

Does one simply delete the svn:externals link once the tag is created?

2. In the case of common code shared between different projects (link from
one to many), how are changes to the projects tracked?

Say, projects 1, 2 and 3 all use common code. If project 1 makes changes
to common (in addition to other changes) and is slated for a release, what
now about projects 2 and 3? They too must be tagged to reflect the changes?
Is the the "normal" practice?

It seems like overhead to have to track and tag all projects affected by

What are other ways of handling this in SVN?


Sorry for the double posts. Not sure what the protocol is on posting to
different lists.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-01-31 18:53:48 CET

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