From owner-freebsd-current Sun Feb 22 16:43:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12726 for freebsd-current-outgoing; Sun, 22 Feb 1998 16:43:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sphinx.lovett.com (root@sphinx.lovett.com [38.155.241.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA12721 for ; Sun, 22 Feb 1998 16:43:22 -0800 (PST) (envelope-from ade@demon.net) Received: from gorgon.lovett.com [38.155.241.3] (ade) by sphinx.lovett.com with esmtp (Exim 1.82 #1) id 0y6lzB-0006nh-00; Sun, 22 Feb 1998 18:43:09 -0600 To: Greg Lehey cc: current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. Organization: Demon Internet Reply-To: ade@demon.net In-reply-to: Your message of "Mon, 23 Feb 1998 10:46:05 +1030." <19980223104605.49121@freebie.lemis.com> Date: Sun, 22 Feb 1998 18:43:08 -0600 From: Ade Lovett Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > >Nate (I think) brought up the fact that people can't always commit >when it would be suitable for my model. Would anybody care to think >about a two-phase commit model: commit to the bleeding edge whenever >you want, commit things that roughly work within a week? Surely that would require a new codeset though, ie: -bleeding -current -stable with all the extra levels of complexity that that incurs. FWIW, I think a good first step would be to have the failures (or otherwise) of Jordan's daily -current build machine made available to the community at large.. it'd certainly be useful in determining whether, for example, my -current build failures are down to the -current tree being broken, or whether local patches and/or other cruft is interfering in some way. Rather than mailing it out to hackers, committers, or wherever, how about adding the daily output of "make world" on the build box somewhere under the CVS tree, so those that are interested can cvsup a new category (say "builds"), and those that aren't don't end up with unwanted stuff in their mailboxes. -aDe -- Ade Lovett, Demon Internet, Austin, Texas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message