On 7/26/06, Scott Ullrich <[EMAIL PROTECTED]> wrote:
On 7/26/06, Rob Terhaar <[EMAIL PROTECTED]> wrote:
> i'm curious, what sort of things have been found wrong with cvs_sync.sh in
> RELENG_1? Personally, I've been doing cvs_sync.sh on one of my routers at
> the office here for a couple months with no issues. But i'd like to know
> what to watch out for?
>
> ...but I'll defiantly be installing the full RC2 update when it's released
> :D
#1. Numerous people claiming to cvs_sync.sh releng_1 but end up on -HEAD
#2. If we commit something to the cvs repo to build a iso and test
and someone syncs in between, etc...
We commit a bad patch and a dozen people get it and break their
systems. Also, cvs_sync.sh doesn't sync FreeBSD, so you're left with
systems that claim they're running current code, but aren't. Nope,
cvs_sync.sh is gone for now, we've got new build servers that have
disk space and capacity to release snapshots more frequently.
--Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
