From owner-freebsd-stable Mon May 29 22:11: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from epsilon.lucida.qc.ca (epsilon.lucida.qc.ca [216.95.146.6]) by hub.freebsd.org (Postfix) with ESMTP id 4E94E37BD3B for ; Mon, 29 May 2000 22:11:02 -0700 (PDT) (envelope-from matt@ARPA.MAIL.NET) Received: from localhost (matt@localhost) by epsilon.lucida.qc.ca (8.9.3/8.9.3) with ESMTP id BAA53264; Tue, 30 May 2000 01:11:02 -0400 (EDT) (envelope-from matt@ARPA.MAIL.NET) X-Authentication-Warning: epsilon.lucida.qc.ca: matt owned process doing -bs Date: Tue, 30 May 2000 01:11:00 -0400 (EDT) From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: Doug Barton Cc: FreeBSD-STABLE Subject: Re: 4.0-stable, OpenSSH v1 & v2 In-Reply-To: <393349CC.66070C95@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 30 May 2000, Doug Barton wrote: [...] : Think about that for a minute. Do we still want to support FreeBSD : 2.1.x in the ports? Assuming the answer is no, all Kris is saying is : that when we stop supporting 3.x, the openss[hl] ports will disappear. : Please don't overreact. :) When you put it like that, I agree with you. However, when the ports versions are always kept up to date and get updated far quicker than changes merge into the -stable source tree (for obvious reasons, I'm not criticizing that.), I don't see why we should make it difficult for people to use current versions of software. I'm not overreacting or panicing, I'm simply thinking ahead in the future like I always do :) : Doug Matt Heckaman matt@arpa.mail.net http://www.lucida.qc.ca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: http://www.lucida.qc.ca/pgp iD8DBQE5M01mdMMtMcA1U5ARApzKAKDc31bcNkFEedp25G6xfQjk+EZgOQCfevvA 0ONNgFvBbuDKF5Aq8noHbuA= =gJwl -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message