On Thu, 2006-10-05 at 17:25 -0700, David Dyer-Bennet wrote: > > Well, unless you have a better VCS than CVS or SVN. I first met this > as an obscure, buggy, expensive, short-lived SUN product, actually; I > believe it was called NSE, the Network Software Engineering > environment. And I used one commercial product (written by an NSE > user after NSE was discontinued) that supported the feature needed. > Both of these had what I might call a two-level VCS. Each developer > had one or more private repositories (the way people have working > directories now with SVN), but you had full VCS checkin/checkout (and > compare and rollback and so forth) within that. Then, when your code > was ready for the repository, you did a "commit" step that pushed it > up from your private repository to the public repository. > > One of the big problems with CVS and SVN and Microsoft SourceSafe is > that you don't have the benefits of version control most of the time, > because all commits are *public*.
Just FYI: that buggy, expensive, short-lived SUN product eventually became "Teamware". Check out (no pun intended) Mercurial and similar products, which have similar behavior to Teamware - each developer has a "workspace" for code, and you can do VC inside that workspace without having to do a putback into the "main" tree. That way, you do frequent VC checkins, but don't putback to the main tree until things actually work. Or, at least, you _claim_ them to work. :-) -- Erik Trimble Java System Support Mailstop: usca14-102 Phone: x17195 Santa Clara, CA Timezone: US/Pacific (GMT-0800) _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
