>-----Original Message-----
>From: Jared Silva [mailto:jayrod@gmail.com]
>Sent: Friday, April 27, 2007 1:51 PM
>To: users
>Subject: Re: Subversion vs Clearcase
>
>Chris.Fouts@qimonda.com wrote:
>> My bad! CC has a config spec that provides a way to pick and choose,
>> or "filter" what files can be in a build. What's neat about
>it, I can
>> mix and match any trunked, tagged, or branched files in the
>repos. For
>> example, I can
>>
>> element foo.c /b_R1/2
>> element * /b_R1/latest
>> element * /main/latest
>>
>> This means, in this order...
>> 1. Use v2 of foo.c from the b_R1 branch 2. Use b_R1 branch for the
>> rest of the files,
>> if the files are on that branch
>> 3. Use the /main/latest version of the rest of
>> files
>>
>> If I remove the second line, I'll ignore the b_R1 branch, except for
>> foo.c /b_R1/2, ON THE FLY.
>>
>> I may have added the top line because I found a problem with the
>> /b_R1/latest version of foo.c (say v3), so I elected to use v2
>> instead.
>>
>> I can "commit" changes using config specs.
>
>Creating a Complex Tag
>http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.htm
>l#svn.branchmerge.tags.mkcomplex
>
>It is probably more effort to set up with Subversion, but doable.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
Thanks for the link, but I read it and don't quite follow. Please
explain how complex tags can be act like a "confg spec?"
- How can I use it to checkout the files I need, and then work with
those files?
- How can I use it to tag (label?) those files?
- How can I use it to then commit the changes?
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 30 16:44:29 2007