From owner-freebsd-current@FreeBSD.ORG  Sun Sep 21 00:44:32 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 3DCD116A4C0
	for <current@freebsd.org>; Sun, 21 Sep 2003 00:44:32 -0700 (PDT)
Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2F2DD43FE1
	for <current@freebsd.org>; Sun, 21 Sep 2003 00:44:31 -0700 (PDT)
	(envelope-from linimon@lonesome.com)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id C84B8140AB; Sun, 21 Sep 2003 02:44:30 -0500 (CDT)
Date: Sun, 21 Sep 2003 02:44:30 -0500 (CDT)
From: Mark Linimon <linimon@lonesome.com>
X-X-Sender: linimon@pancho
To: Daniel Eischen <eischen@vigrid.com>
In-Reply-To: <Pine.GSO.4.10.10309210134060.26520-100000@pcnet5.pcnet.com>
Message-ID: <Pine.LNX.4.44.0309210241270.27516-100000@pancho>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: h@schmalzbauer.de
cc: current@freebsd.org
cc: "M. Warner Losh" <imp@bsdimp.com>
cc: Kris Kennaway <kris@obsecurity.org>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Sep 2003 07:44:32 -0000

> I don't think committing fixes for -current breakages should cause
> problems for 4.9-RELEASE (especially with the caveat that they be
> compile tested on -stable).

It takes several days to do the compile QA.  That's assuming
that no actual users are allowed to have time to test the changes
before the release is cut.

IMHO, what you think just doesn't reflect the actual reality
involved.  We are just going to have to disagree on this.

You should really look at the bento logs and get an understanding
of the continual QA that is done on the _over_ 9000 ports (many
of which have _no_ maintainer signed up) before you make assumptions
that there shouldn't be significant problems with what you propose.

mcl