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

[Subversion] Rational Rhapsody files, lock unlock philosophy

From: Keller Eric <Ekeller_at_hamilton-medical.ch>
Date: Wed, 10 Aug 2011 17:21:44 +0200

Hi everybody,

We are finally switching from PVCS to subversion, and I would like to get more input from you other user concerning the lock/modify/unlock philosophy!

Subversion as PVCS allow the use of locks. The description in your reference book: http://svnbook.red-bean.com/en/1.0/ch02s02.html also presents the Copy modify merge solution, which is more commonly used. Yet our manager people are not convienced that this method is better than a lock unlock modify solution.

For giving you a short overview the project files revision in subversion are Rhapsody models, these files data structure is ASN.1(Abstract Syntax Notation One) It is not binary.

Are there other user using subversion associated with Rhapsody files who are using the copy-modify-merge solution?

Thank you in advance for your answers, I am looking forward for a constructive communication!

Best Regards

--
Eric Keller
Eric Keller
_________________________________________
Software Engineer
HAMILTON Medical AG
Via Crusch 8
7402 Bonaduz
Switzerland
Phone:+41 81 660 65 16
Fax:+41 81 660 60 20
eMail:Ekeller_at_hamilton-medical.ch
Web:www.hamilton-medical.ch
Received on 2011-08-10 17:55:22 CEST

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.