Some clarifications, based on a couple questions I have received: - This is for the onnv-clone module on onnv.sfbay. It's accessible via an rsync source path of onnv.sfbay::onnv-clone.
- This is NOT the preferred method for keeping a clone up to date, it will merely continue to work if you were already using it. For keeping a remote clone repository up to date, please use Mercurial. - This IS useful for stuff that lives in the clone, but is not under source code management. For example, cscope databases. Though these days, I imagine you could build them yourself with reasonably efficiency. --Mark On Mon, 11 Aug 2008, Mark J. Nelson wrote: > Date: Mon, 11 Aug 2008 11:10:18 -0600 > From: Mark J. Nelson <Mark.J.Nelson at Sun.COM> > To: on-discuss at opensolaris.org > Subject: heads up: rsync path changed for onnv-clone > > > External users may ignore this note. > > I have updated /etc/rsyncd.conf on the gate machine such that [onnv-clone] > now points to the new, Mercurial clone repository. If you're using rsync for > things like cscope, or keeping a current clone, it should continue to > function correctly. > > If you're looking for rsync access to the old, frozen-at-build-96, static, > teamware workspace, please let me know. > > --Mark > >
