Ryan, > Yes, instead of using "svn copy" to create the tag, use the > svncopy.pl script available here: > > http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svncopy/
Thanks, I will take a look at into this. Is this also achievable from the GUI with TortoiseSVN? The next obvious question for you (or svn admins?) is: Instead of having a decadency on Perl & .pl script, wouldn't it make sense to integrate this feature directly into an svn command/argument? I am making the suggestion to make the product more user friendly and powerful. In previous company, I have used Perforce, and they really make this easy. Cheers, Charles --- On Sat, 1/30/10, Ryan Schmidt <subversion-20...@ryandesign.com> wrote: > From: Ryan Schmidt <subversion-20...@ryandesign.com> > Subject: Re: svn:externals & tagging, how to combine code between teams > To: "Charles Chan" <cchan...@yahoo.com> > Cc: users@subversion.apache.org > Received: Saturday, January 30, 2010, 8:29 AM > > On Jan 29, 2010, at 22:12, Charles Chan wrote: > > > The main problem we are having is with the behavior of > 'svn tag' in association with externs. > > Of course, there is no command "svn tag"; to make a tag or > branch, you just "svn copy" the trunk. > > > The current externs are referencing the HEAD -- > because we would like to build the latest version regularly > to ensure all modules works together. However, once a build > is successful and we proceed to make a release, it would be > nice if there was an easy way to automatically tag > everything -- including the version used in the extern. > > Yes, instead of using "svn copy" to create the tag, use the > svncopy.pl script available here: > > http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svncopy/ > > > > __________________________________________________________________ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com.
