From owner-freebsd-current@FreeBSD.ORG Sat Sep 20 21:01:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4F8216A4B3; Sat, 20 Sep 2003 21:01:29 -0700 (PDT) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B6E643FDF; Sat, 20 Sep 2003 21:01:27 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: from freebsd1.cimlogic.com.au (localhost [127.0.0.1]) by cimlogic.com.au (8.12.9/8.12.9) with ESMTP id h8L43evl031486; Sun, 21 Sep 2003 14:03:40 +1000 (EST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.12.9/8.12.9/Submit) id h8L43eQZ031485; Sun, 21 Sep 2003 14:03:40 +1000 (EST) Date: Sun, 21 Sep 2003 14:03:40 +1000 From: John Birrell To: Kris Kennaway Message-ID: <20030921040340.GC28195@freebsd1.cimlogic.com.au> References: <20030920.164621.68039520.imp@bsdimp.com> <20030921022407.GA39970@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030921022407.GA39970@rot13.obsecurity.org> User-Agent: Mutt/1.4.1i cc: deischen@freebsd.org cc: current@freebsd.org cc: "M. Warner Losh" cc: h@schmalzbauer.de Subject: Re: Fixing -pthreads (Re: ports and -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 04:01:29 -0000 On Sat, Sep 20, 2003 at 07:24:07PM -0700, Kris Kennaway wrote: > 3) You, John Birrell, and whoever else is interested in fixing these > ports can work on them at your own pace without disrupting life for > the rest of the users. Once they're all fixed, we can turn the error > back on or make it a NOP or do whatever else is decided to be > appropriate. OK, so what's the commit procedure going to be? This could generate an awful lot of little PRs. Scot posted a patch for bsd.port.mk. Is that going to be committed? That's needed. Are you prepared to unlock the ports tree and allow a blanket commit auth for commits that only change patch-configure? That should catch most of the simple cases. -- John Birrell