From owner-freebsd-current Wed Feb 25 07:08:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00736 for freebsd-current-outgoing; Wed, 25 Feb 1998 07:08:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from marathon.tekla.fi (marathon.tekla.fi [192.98.7.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00711 for ; Wed, 25 Feb 1998 07:08:43 -0800 (PST) (envelope-from sja@tekla.fi) Received: from poveri.tekla.fi (poveri.tekla.fi [192.98.7.19]) by marathon.tekla.fi (8.8.7/8.8.7) with SMTP id RAA23437 for ; Wed, 25 Feb 1998 17:08:05 +0200 From: Sakari Jalovaara Received: by poveri.tekla.fi; (5.65v3.2/1.1.8.2/20Aug96-0557PM) id AA29901; Wed, 25 Feb 1998 17:08:05 +0200 Date: Wed, 25 Feb 1998 17:08:05 +0200 Message-Id: <9802251508.AA29901@poveri.tekla.fi> To: freebsd-current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'd like a system where I could 'pend a commit' and have it run > through a build-test and then be committed if it passed (and no one > else had touched the files I've been working on in the meantime). Or, for a simpler system: run "rm -rf /usr/obj; make" in a loop on a dedicated box. If build fails, automatically send "tail -100 make.out" to everyone who has committed in the last few hours. Pro: a useful service for committers who can't (or can't be bothered to) make world always. Con: requires a fast-ish extra build box. May tempt folks to test their changes less "'cos the build box will do it anyway". ++sja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message