From owner-freebsd-bugs Fri Mar 31 8: 0: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id EDF9F37BADE for ; Fri, 31 Mar 2000 08:00:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id IAA40039; Fri, 31 Mar 2000 08:00:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Fri, 31 Mar 2000 08:00:03 -0800 (PST) Message-Id: <200003311600.IAA40039@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Jin Guojun (FTG staff) Subject: Re: bin/16271 Reply-To: Jin Guojun (FTG staff) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/16271; it has been noted by GNATS. From: Jin Guojun (FTG staff) To: sheldonh@uunet.co.za Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/16271 Date: Fri, 31 Mar 2000 07:54:39 -0800 (PST) > > This problem also exists in 4.0 release. The patch is very simple, > > and the concept is clear. Can we fix this problem with apply the > > following patch? > > I don't think so, because that file is on the vendor branch. This fix > should be submitted to keith Bostic, nvi's maintainer. If he agrees > that the next release of nvi will include this patch exactly, then we > can probably do some magic. Then, how can I contact keith Bostic? Has he been notified for this problem yet? -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message