I'm located in Romania - GMT+2.

I guess others have made clear their point: while is it possible to have 
only one big fat VCX, that will force you to use some third-party tools to 
do the merge operation. Try doing your best explaining your boss why is 
better to have multiple smaller vcx-es.

There is one question nobody asked: how many people will actually do the 
development? I'm thinking maybe your boss just wants to have a history of 
changes (and he doesn't do any development by himself) and you're the only 
one which actually writes code. In this case you won't have to merge 
anything, so the CVS+1 big VCX would work pretty well.

----- Original Message ----- 
From: "Paul Newton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 17, 2007 3:51 PM
Subject: Re: CVS and visual classes


> Tx Grigore
>
> Grigore Dolghin wrote:
>> Nope - Copy-Modify-Merge model won't work. You really don't want to merge
>> two binary files, aren't you?
>>
> No :-(
>> If you guys need someone to set that thing up, I can help you in this
>> matter. I would also suggest using Subversion + Tortoise instead pure CVS
>> (Subversion is CVS-based, does the same thing and IMO is better) and
>> Tortoise integrates in windows shell. Just right click the folder and
>> "commit".
>>
>
> Where are you based Grigore ?  I will pass this on ... but would you be
> able to set something up and still have us keep all our classes in the
> one VCX ?
>
> Paul Newton
>
>
>
[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to