From owner-freebsd-current@FreeBSD.ORG Sat Sep 20 22:55:03 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 CABF016A4B3; Sat, 20 Sep 2003 22:55:03 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-107-253.dsl.lsan03.pacbell.net [64.169.107.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 385A243FBF; Sat, 20 Sep 2003 22:55:01 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id C3A0666D6A; Sat, 20 Sep 2003 22:54:53 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id DC7757CA; Sat, 20 Sep 2003 22:54:53 -0700 (PDT) Date: Sat, 20 Sep 2003 22:54:53 -0700 From: Kris Kennaway To: deischen@freebsd.org Message-ID: <20030921055453.GA40942@rot13.obsecurity.org> References: <20030921053059.GA40776@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rwEMma7ioTxnRzrJ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: h@schmalzbauer.de cc: current@freebsd.org cc: "M. Warner Losh" cc: Kris Kennaway 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 05:55:03 -0000 --rwEMma7ioTxnRzrJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 21, 2003 at 01:44:35AM -0400, Daniel Eischen wrote: > 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). Out of curiosity, what's the reason > the tag can't be laid now? In a better world, freezing -stable > shouldn't hinder -current. There are other fixes that are still being committed. It was a release engineering decision to upgrade kde and gnome for 4.9-R, and there are still bugs being shaken out as a result. Since you (and others who have expressed similar puzzlement about the need for ports freezes) are not involved in the actual mechanics of FreeBSD release engineering, please just try to accept that there are technical challenges in making sure that things don't go wrong at the last minute, and the way we try to make sure the release doesn't get botched up by a poorly-considered change at the 11th hour is by enforcing a period of quietude on the tree so that there's a reasonable chance that any problems will be detected before the release instead of after. This is the reality of it, and wishing that things were different just isn't productive right now. > > What, precisely, do you object to in the above proposal? >=20 > 1, 2, and 3. I don't think backing out -pthread change helps > much in fixing ports... Again, why? Please explain instead of asserting, because that's getting us nowhere towards resolving this. Kris --rwEMma7ioTxnRzrJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/bT0tWry0BWjoQKURAmWSAJ9SeAYSx+0Mzaj6oZJ3ALBUz9w9ZQCfdp9R i6BV4BabhA5jUM9jahF/1Mw= =mO6B -----END PGP SIGNATURE----- --rwEMma7ioTxnRzrJ--