Date: Tue, 1 Aug 2000 13:39:14 -0700 (PDT) From: Kris Kennaway <kris@hub.freebsd.org> To: Darren Reed <darrenr@reed.wattle.id.au> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: [spam score 6.00/10.0 -pobox] Re: [spam score 3.31/10.0 -pobox] Re: cvs commit: src/sys/netinet ip_fil.c ip_fil.h ip_input.c ip_ Message-ID: <Pine.BSF.4.21.0008011334250.28502-100000@hub.freebsd.org> In-Reply-To: <200008011405.AAA06448@avalon.reed.wattle.id.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Aug 2000, Darren Reed wrote:
> Which box is the "build box" ?
beast (5.0 alpha), ref4 (4.x) and ref5 (5.0 i386) are build machines.
> For once I tried to do a "remote commit" (rather than from freefall,
> et al) but it appears to have had had some drawbacks. Having seen
> comments about "expect -current to be broken over the next X months",
> I'm not sure what the stink is all about. This isn't a commit to
> -STABLE, after all.
That's simply not true - we have the same expectations for code entering
-current as we always have had (namely, that the committer should have
taken reasonable steps to assure it actually compiles, and is
tested). When -current is gratuitously broken it becomes difficult or
impossible for other developers to work from it (most of the developers
run -current on their primary work machines, I'd guess).
What you probably heard was discussion about the SMP changes which are in
development: those probably will have an unavoidable affect on the
stability of -current for an extended period, but it's not an excuse to
break things in other directions.
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <forsythe@alum.mit.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0008011334250.28502-100000>