From xemacs-m  Thu Mar 27 19:13:06 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id TAA28933
	for <xemacs-beta@xemacs.org>; Thu, 27 Mar 1997 19:13:04 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	for 
	id QQcitg04844; Thu, 27 Mar 1997 20:13:06 -0500 (EST)
Date: Thu, 27 Mar 1997 20:13:06 -0500 (EST)
Message-Id: <QQcitg04844.199703280113@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Un-fixed problem #2 in 19.15-really-final
In-Reply-To: <199703272017.PAA15646@amber.vis-av.com>
References: <199703272017.PAA15646@amber.vis-av.com>
X-Mailer: VM 6.23 under 19.15 XEmacs Lucid
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

I don't think the TM or VM flaw reports are relevant to XEmacs.
Best to discuss those on their appropriate lists I think.  If
the bug/flaw is in XEmacs itself, then the package author or
designate can report it here.  A good idea for the rest of the major
packages too, probably.

