>-----Original Message----- >From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] >On Behalf Of Ben Hencke >Sent: 08 December 2004 17:45 >To: Microcontroller discussion list - Public. >Subject: Re: [PIC] Version Control System? > > >On Wed, 8 Dec 2004 10:36:35 -0000, Michael Rigby-Jones > wrote: >> >> >> >> We currently use Visual Source Safe which is perfectly adequate for >> our small team. Recently we attempted (and failed) to move over to >> Neuma CM+ which appears to be the most complex, fragile and hard to >> use bit of software I have ever found. >> > >Ick! I have to use SourceSafe all the time, and it is a nasty >nasty version control system. The checkout/checkin model is >insufficience even for a 2 person development team if you work >on the same files. It is even worse if you have intermittent >access to the server ie remote development/travel/dialup >access. It locks all of the files that you do not checkout >making it a huge pain to go back and forth to checkout/checkin >for every file. If you don't checkout just the files you need, >you end up blocking other people from checking out the files. I agree that for shared code development it has serious limitations. We most always work on individual projects however, and have had no major problems in the last 6 years. For this kind of work, it excels in it's simplicity. The main reason it was chosen is that we already were using it for Visual Studio projects. >I have lost several days of work due to it overwriting my >changed files that I could not checkout because I was on the >road -- without any warning or recourse. There are some that >might disagree, but I think that your version control system >shouldn't require you to make backups of your code before using it. I don't know how you managed to achieve this, it always given a warning when checking out if the files in the working directory have been modified. Regards Mike ======================================================================= This e-mail is intended for the person it is addressed to only. The information contained in it may be confidential and/or protected by law. If you are not the intended recipient of this message, you must not make any use of this information, or copy or show it to any person. Please contact us immediately to tell us that you have received this e-mail, and return the original to us. Any use, forwarding, printing or copying of this message is strictly prohibited. No part of this message can be considered a request for goods or services. ======================================================================= _______________________________________________ http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist