On October 5, 2006 5:25:17 PM -0700 David Dyer-Bennet <[EMAIL PROTECTED]> 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.
I wouldn't call that 2-level, it's simply branching, and all VCS/SCM systems have this, even rcs. Some expose all changes in the private branch to everyone (modulo protection mechanisms), some only expose changes that are "put back" (to use Sun teamware terminology). Both CVS and SVN have this. -frank _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
