Hi,
In our company, we are working on a product composed of different C/C++
modules. Ideally, each tier and module should be developed by separately by
different teams and tested independently. Currently, we have separate each
module into it's own branch:\
The modules are:
\hid
\branches
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 --
l.
In previous company, I have used Perforce, and they really make this easy.
Cheers,
Charles
--- On Sat, 1/30/10, Ryan Schmidt wrote:
> From: Ryan Schmidt
> Subject: Re: svn:externals & tagging, how to combine code between teams
> To: "Charles Chan"
> Cc: users@subver
On Jan 30, 2010, at 10:08, Charles Chan wrote:
>> 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 achiev
