Date: Tue, 12 Jun 2001 14:55:16 -0700 From: W Gerald Hicks <gehicks@cisco.com> To: jim@compete.com Cc: Mark Evenson <evenson@panix.com>, stable@FreeBSD.ORG Subject: Re: Why is the STABLE branch not so stable anymore? Message-ID: <3B268FC4.A749B300@cisco.com> References: <Pine.A41.3.96.1010612000229.84080E-100000@gsaix2.cc.GaSoU.EDU> <3B25CAEC.27AF9D30@cisco.com> <a0zobdeq46.fsf@panix6.panix.com> <3B265CE9.516AFB04@cisco.com> <20010612163457.A6283@cartman.boston.geekhouse.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Uhm, there's also anoncvs.freebsd.org: > > % setenv CVSROOT ":pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs" > % cvs login > (Logging in to anoncvs@anoncvs.FreeBSD.org) > CVS password: > % > > - jim > (waves to jim) Yes, anoncvs is available too but to me it seems to be a rather limited resource (a server of one). I wasn't sure if it was good to advocate that people start using that regularly for maintenance of their "production servers". It certainly works though, I've used it before. :-) On the other hand, CVSup mirrors are dispersed worldwide and the protocol used by CVSup is _much_ friendlier in terms of bandwidth utilization (once synched anyway). Accessing history or logs is pretty zippy with the local repo model. What I do here is to maintain a local mirror using /usr/ports/net/cvsup-mirror. Other systems access the local repo using CVSup or cvs server mode, depending on what we're up to at any given moment. However one does it, the point is that these transient glitches with -stable need not cause too much consternation. When it happens it's very trivial to recover from and one's energy can be more profitably directed at being part of the solution. Send-pr is the correct way to help. Cheers, Jerry Hicks gehicks@cisco.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B268FC4.A749B300>