Date: Sun, 21 Sep 2003 14:03:40 +1000 From: John Birrell <jb@cimlogic.com.au> To: Kris Kennaway <kris@obsecurity.org> Cc: h@schmalzbauer.de Subject: Re: Fixing -pthreads (Re: ports and -current) Message-ID: <20030921040340.GC28195@freebsd1.cimlogic.com.au> In-Reply-To: <20030921022407.GA39970@rot13.obsecurity.org> References: <20030920.164621.68039520.imp@bsdimp.com> <Pine.GSO.4.10.10309202038570.19227-100000@pcnet5.pcnet.com> <20030921022407.GA39970@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030921040340.GC28195>