Folks, The Clearview Mercurial repositories are open for business.
ssh://hg.opensolaris.org/hg/clearview/clearview-ipobs ???ssh://hg.opensolaris.org/hg/clearview/clearview-noipmp ???ssh://hg.opensolaris.org/hg/clearview/clearview-ipmp ???ssh://hg.opensolaris.org/hg/clearview/clearview clearview-ipobs is a child of onnv-clone and contains the IP Observability Devices component. clearview-noipmp is a child of cleraview-ipobs and contains the removal of the kernel IPMP implementation currently in onnv. clearview-ipmp is a child of clearview-noipmp and contains the Clearview IPMP Rearchitecture component. The clearview repository is a child of clearview-ipmp, and contains all of the above including the IP Tunneling Device Driver component of Clearview. ???Members of the Clearview team have full read/write access to these repositories using their opensolaris id's, and there is anonymous read-only access using the "anon" user (e.g., ssh://anon at hg.opensolaris.org/hg/...). Once the opengrok team resolves its shortage of disk-space problems, all of the project's source will also be available for browsing at: http://opensolaris.org/sc/src/clearview/ Notification of "hg push" events to these gates are configured to go to clearview-discuss at opensolaris.org, although if it seems more appropriate to shorten the list, please let me know and I can change it and/or setup a different list for this purpose. I'm still working out the details of the mechanics of regular builds and merges with onnv-clone and between clearview repositories, so I'll have more on that as I work these things out. For now, there is no reason for team members not to continue development using these repositories. To save on network bandwidth (at least theoretically), I would suggest initially cloning a local (or as local as possible) onnv repository to your development workspace prior to pulling from these repositories. -Seb
