[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-30 20:36:42 CEST

>-----Original Message-----
>From: Les Mikesell [mailto:lesmikesell@gmail.com]
>Sent: Monday, April 30, 2007 2:10 PM
>To: Fouts Christopher (QNA RTP PT PREV)
>Cc: users@subversion.tigris.org
>Subject: Re: Subversion vs Clearcase
>
>Chris.Fouts@qimonda.com wrote:
>
>> Don't get me wrong, I really like SVN - espcially for the price! I'm
>> appreciative of the fact that people are passionate enough
>to come up
>> with an app. that I use everyday in my company. I'm just merely
>> pointing out the one SCM feature I like about other similar apps.
>
>Just think of branching as the main SCM strategy in svn and it
>may make more sense. If you want to work on something that
>you don't want to match an existing revision, put it together
>in a new branch.
>
>Also, if you are starting a new project from scratch, you
>might want to organize it differently for svn. The possible
>ways to mix components are the 'svn switch' approach at
>directory levels in the same tree, or using externals to pull
>in things that are not in the same tree in the repository.
>The latter approach is probably better for libraries or code
>shared by other projects where you want the option of floating
>with the development HEAD or locking to a known revision (in
>early stages you may need to coordinate work in both, but as
>you approach a release you probably want to tie them to tags
>to avoid problems from future changes that might be made for
>other projects.
>
>--
> Les Mikesell
> lesmikesell@gmail.com
>

Thanks, I'll try these ideas!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 30 20:37:00 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.