From 2f5d5a1f5381c5f35e5f3432bacf9b52b0f71ee6 Mon Sep 17 00:00:00 2001
From: sperber <sperber>
Date: Thu, 16 Jan 2003 13:34:58 +0000
Subject: [PATCH] Remove obsolete comments.

---
 scheme/lib/ftp.scm | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/scheme/lib/ftp.scm b/scheme/lib/ftp.scm
index 73206d8..a46da0c 100644
--- a/scheme/lib/ftp.scm
+++ b/scheme/lib/ftp.scm
@@ -6,14 +6,6 @@
 ;;; For copyright information, see the file COPYING which comes with
 ;;; the distribution.
 
-;;; Unimplemented =====================================================
-;;
-;; This module has no support for sites behind a firewall (because I
-;; am unable to test it). It shouldn't be very tricky; it only
-;; requires using passive mode. Might want to add something like the
-;; /usr/bin/ftp command `restrict', which implements data port range
-;; restrictions.
-;;
 ;; The following rfc959 commands are not implemented:
 ;;
 ;; * ACCT (account; this is ignored by most servers)
@@ -45,12 +37,9 @@
 
 ;;; TODO ============================================================
 ;;
-;; * handle passive mode and firewalls
 ;; * Unix-specific commands such as SITE UMASK, SITE CHMOD
-;; * object-based interface? (like SICP message passing)
 ;; * improved error handling
 
-;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
 ;; Communication is initiated by the client. The server responds to
 ;; each request with a three digit status code and an explanatory
 ;; message, and occasionally with data (which is sent via a separate,
@@ -78,7 +67,6 @@
 ;; extracted information, or #f to indicate failure. Other procedures
 ;; return a "status", which is either the server's reply as a string,
 ;; or #f to signify failure.
-;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
 
 ;; beware, the log file contains password information!