Date: Sun, 5 Dec 1999 10:43:29 +0100 (CET) From: Nick Hibma <hibma@skylink.it> To: Matthew Jacob <mjacob@feral.com> Cc: Mike Smith <msmith@FreeBSD.org>, "Matthew N. Dodd" <winter@jurai.net>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern subr_bus.c Message-ID: <Pine.BSF.4.20.9912051039190.297-100000@henny.jrc.it> In-Reply-To: <Pine.BSF.4.05.9912041408480.368-100000@semuta.feral.com>
index | next in thread | previous in thread | raw e-mail
What about the nightly builds of world and the output of that? It should
not be too difficult to drop that into a message and send the tail of
that off to committers when the build fails at some stage.
Add a do { } while(1) around it and include LINT (and an alpha cross
build when that is possible) in the build of the kernel and you uncover
most breakages as soon as possible.
As a side effecy you are left with the most recent SNAP build of that
day.
Nick
> > Yet again, I'll point out that we've already been through this, and while
> > it might work for a corporate, 9-to-5 environment it's not going to fly
> > for our distriuted model.
> >
> > OTOH, the Mozilla folks have already been through this process and come
> > out the other side with a much better tool for the job. It's called
> > 'tinderbox', and if anyone is motivated enough by _this_ round of the
> > conversation to actually do anything about it, we can certainly arrange a
> > small cluster to do the backend processing.
>
> While this is very positive, I'd have to say that this is a bit of
> overkill. All people need to do is to remember to practice safe
> integration. It's not really that complicated.
>
>
>
--
hibma@skylink.it
n_hibma@freebsd.org USB project
http://www.etla.net/~n_hibma/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.9912051039190.297-100000>