From owner-freebsd-ports  Sun Aug 23 15:27:13 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA00581
          for freebsd-ports-outgoing; Sun, 23 Aug 1998 15:27:13 -0700 (PDT)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00576
          for <ports@FreeBSD.ORG>; Sun, 23 Aug 1998 15:27:11 -0700 (PDT)
          (envelope-from asami@sunrise.cs.berkeley.edu)
Received: from bubble.didi.com (sji-ca10-63.ix.netcom.com [205.186.214.63]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id PAA19383; Sun, 23 Aug 1998 15:26:27 -0700 (PDT)
Received: (from asami@localhost)
	by bubble.didi.com (8.8.8/8.8.8) id PAA02297;
	Sun, 23 Aug 1998 15:26:22 -0700 (PDT)
	(envelope-from asami)
Date: Sun, 23 Aug 1998 15:26:22 -0700 (PDT)
Message-Id: <199808232226.PAA02297@bubble.didi.com>
To: sfarrell@healthquiz.com
CC: ports@FreeBSD.ORG
In-reply-to: <87k93z4fvh.fsf@couatl.uchicago.edu> (message from stephen farrell on 23 Aug 1998 15:12:18 -0500)
Subject: Re: [comp.infosystems.www.browsers.ms-windows,comp.infosystems.www.browsers.misc,comp.infosystems.www.browsers.x,de.comm.infosystems.www.browsers,fj.net.infosystems.www.browsers] ANNOUNCE: 128-bit crypto: Fortify for Netscape v1.2.6 released
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

 * I think this means that fortify for the current port of 4.06 is
 * broken...

This seems to happen at every upgrade.  How about we make
netscape4-{c*,n*}-fortify ports so they can be tracked separately?
Is that ok, Andrey?  (And who wants to be the maintainer of the
*-fortify ports?)

Satoshi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message