From owner-cvs-ports Thu Jun 20 12:22:43 1996 Return-Path: owner-cvs-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02749 for cvs-ports-outgoing; Thu, 20 Jun 1996 12:22:43 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02744; Thu, 20 Jun 1996 12:22:40 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id MAA21586; Thu, 20 Jun 1996 12:22:12 -0700 (PDT) To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) cc: jkh@freefall.freebsd.org (Jordan K. Hubbard), CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-ports@freefall.freebsd.org Subject: Re: cvs commit: ports/net/ncftp - Imported sources In-reply-to: Your message of "Thu, 20 Jun 1996 22:56:01 +0400." <199606201856.WAA01348@astral.msk.su> Date: Thu, 20 Jun 1996 12:22:12 -0700 Message-ID: <21583.835298532@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-cvs-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Jordan, you can remove it completely, it is very obsoleted. Well some folks have suggested that it still does a few things correctly that ncftp2 does not, and I personally have had weird problems with ncftp2 myself where it simply drops the connection with the server for no discernable reason. I use ncftp every day, and for reasons of backwards-compatibility I see no reason not to leave it as 1.x for now? Yes, someday it would be nice to have a single tool again but let's have a short transition period first - I _just_ kicked it out of the tree, and some people are going to complain about that. I'd prefer to be able to simply point them at the port. Jordan