Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Sat, 18 Nov 2000 17:25:10 -0500 From: Chris Faylor To: cygwin-apps AT cygwin DOT com Cc: bli AT eecg DOT toronto DOT edu Subject: [bli AT eecg DOT toronto DOT edu: Pine 4.30 port for cygwin 1.1.5] Message-ID: <20001118172510.A7519@redhat.com> Mail-Followup-To: cygwin-apps AT cygwin DOT com, bli AT eecg DOT toronto DOT edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i Can anyone fill this person in on what is required? cgf ----- Forwarded message from Baochun Li ----- From: Baochun Li To: cgf AT redhat DOT com Subject: Pine 4.30 port for cygwin 1.1.5 Date: Sat, 18 Nov 2000 15:27:39 -0500 Hi Christopher, I have made an experimental Pine 4.30 port of Cygwin 1.1.5, based on a previous Pine 4.10 port for B20.1. Up till now I have not had negative experiences with this port. Details of the port can be found at: http://www.eecg.toronto.edu/~bli/personal.html I recently saw your "call for ports" in the cygwin-apps mailing list. If the port turns out to be stable enough (I'm trying it out every day), it may be a candidate for an official Pine port for Cygwin 1.1.x, which could be put in the cygwin official tree. Please let me know what you think. Thanks, Baochun -- Baochun Li, Assistant Professor Department of Electrical and Computer Engineering University of Toronto ----- End forwarded message ----- -- cgf AT cygnus DOT com Red Hat, Inc. http://sources.redhat.com/ http://www.redhat.com/