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

Re: limitations of svn:externals

From: Russell Hind <rh_gmane_at_mac.com>
Date: 2005-11-07 12:50:20 CET

Molle Bestefich wrote:
> Narayana Prasad wrote:
>> But the common code must stay common and
>> maintain a common history.
> Except in the case of 'svn cp' to branches or tags.
> When you branch or tag, you want an actual repository copy of your
> common files, fixated at the version that is in use when you release
> (or branch).

Yes, we use externals for 'proper' externals in another repo, and for
links to common code in the same repo. For the proper externals, on a
copy we'd like to be able to have the -r automatically added to the
external, but with the externals in the same repo, a copy would be required.

Currently we have to do this manually for all our externals when
branching for a release which isn't that usable.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 7 13:04:32 2005

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