[cvsnt] cvsnt for word doc version control

Prochazka, Jan Jan.Prochazka at brooks.com
Mon Feb 12 15:27:29 GMT 2007

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

My 2 cents to discussion "why not VSS".
The main reason why we switched from VSS was that VSS was virtually
unusable over slower cost-to-coast Intranet network. The problem is that
VSS *IS NOT* client-server architecture. It is client only, the server
is file share only. Hence *ALL* repository has to be transferred to the
client *ALL THE TIME* when client wants to do *ANYTHING* with it.
The second reason was file security: We did not have good feeling that
all our source code is buried deep in proprietary MS database and the
database was growing suspiciously fast.


> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org 
> [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Jim Hyslop
> Sent: Monday, February 12, 2007 10:08
> To: Tim Chippington Derrick; cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> Subject: Re: [cvsnt] cvsnt for word doc version control
> Tim Chippington Derrick wrote:
> > We started another project recently (last autumn). We had a big 
> > meeting at the start of the project about version and configuration 
> > management. I argued strongly for CVSNT and a text-based 
> documentation 
> > system, or even using VSS (the agreed project standard :-(  Yuk)
> If you need additional arguments on why to stay away from 
> VSS, have a look at 
> http://www.highprogrammer.com/alan/windev/sourcesafe.html 
> Note that the information on that page is about 5 years old, 
> but most of it is fundamental design issues that have 
> probably not been addressed.
> > got merged, the job wasn't perfect either. So we ended up 
> with a right 
> > mess, with multiple different versions of the document 
> being labelled 
> > v1.1 and v1.2. And don't forget that this was the document that was 
> > supposed to be defining how document version control was to be 
> > managed!
> > 
> > Somebody please give me the strength to carry on living with this...
> If, after that debacle, your co-workers still do not see the 
> problem with your process, then my suggestion is to update 
> your resume and start looking for a new workplace. You're 
> fighting a lost cause, and life is too short to waste time on 
> other peoples' stupidity.
> Meanwhile, you could try to have a Configuration Management 
> expert brought in, and pay this consultant obscene amounts of 
> money just to have him/her tell your boss the same thing 
> you've been trying to say.
> For some reason, management listens more to outside experts 
> than to employees.
> --
> Jim
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs
> _____________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.

This email message, including any attachments, may contain confidential and proprietary information for the sole use of the intended recipient.  If you are not the intended recipient, you are hereby notified that any use, copying or dissemination of this message is strictly prohibited.  If you received this message in error, please notify Brooks Automation, Inc. immediately by reply email or by calling Brooks US Headquarters at +1 978-262-2400. Then delete this message from your system, without making any copy or distribution.  Thank you.

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook