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

RE: Subversion vs Clearcase

From: <Chris.Fouts_at_qimonda.com>
Date: 2007-04-27 18:13:31 CEST

>-----Original Message-----
>From: Andy Levy [mailto:andy.levy@gmail.com]
>Sent: Friday, April 27, 2007 12:00 PM
>To: Fouts Christopher (QNA RTP PT PREV)
>Cc: users@subversion.tigris.org
>Subject: Re: Subversion vs Clearcase
>
>On 4/27/07, Chris.Fouts@qimonda.com <Chris.Fouts@qimonda.com> wrote:
>>
>> >-----Original Message-----
>> >From: Les Mikesell [mailto:lesmikesell@gmail.com]
>> >Sent: Friday, April 27, 2007 11:45 AM
>> >To: Fouts Christopher (QNA RTP PT PREV)
>> >Cc: users@subversion.tigris.org
>> >Subject: Re: Subversion vs Clearcase
>> >
>> >Chris.Fouts@qimonda.com wrote:
>> >> SVN would be my favorite app. only if it had a concept of SCM. If
>> >> it does, can someone shed light on it?
>> >
>> >That might be easier if you explained what you think is
>missing. You
>> >can make branches to isolate work and tags to be able to recall any
>> >version by a name. What else do you need?
>> >
>>
>> I really like the power of a configuration spec in CC; is there
>> something similar in SVN? Thanks!
>
>For the benefit of people who've never used or seen CC (or
>whatever the compared tool du jour is), can folks please
>briefly explain *what* a particular feature does, instead of
>just throwing a name out (if the name doesn't make it
>blindingly obvious)?
>

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.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 27 18:14:51 2007

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