From owner-freebsd-ports  Tue Aug 19 03:05:17 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id DAA25230
          for ports-outgoing; Tue, 19 Aug 1997 03:05:17 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (ala-ca17-23.ix.netcom.com [204.32.168.183])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA25222;
          Tue, 19 Aug 1997 03:05:05 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id DAA20149; Tue, 19 Aug 1997 03:04:11 -0700 (PDT)
Date: Tue, 19 Aug 1997 03:04:11 -0700 (PDT)
Message-Id: <199708191004.DAA20149@silvia.HIP.Berkeley.EDU>
To: kline@thought.org
CC: kline@thought.org, freebsd-ports@FreeBSD.org, me@FreeBSD.org
In-reply-to: <199708190126.SAA21823@tao.thought.org> (message from Gary Kline on Mon, 18 Aug 1997 18:26:35 -0700 (PDT))
Subject: Re: XEmacs-19.15 port is bad
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-ports@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

 * 		The fix is to backpatch from xemacs-19.14; or else
 * 		move upward to the MULE ports, 20.X.  Is this our
 * 		responsibility? or xemacs.org's?  Or is this a 
 * 		dontcare, just do it?  (This is one where I'd roll
 * 		my own fix, rather than burden xemacs.org....  )

I think we should fix xemacs-19.14, and have a new port for
xemacs-20.2.  Maybe two versions of xemacs20, with mule and without
mule.

 * 		Michael, if you're reading this list, now you know 
 * 		all that I have.

I CC:ed to me@freebsd.org.  Michael, if you need more context, I can
forward you the mails.

Satoshi