Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!spool.mu.edu!agate!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: mailer
Message-ID: <1735@toaster.SFSU.EDU>
Date: 16 Jun 91 03:11:54 GMT
References: <3749@opal.cs.tu-berlin.de> <1719@toaster.SFSU.EDU> <1991Jun15.150250.16883@DSI.COM>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 28

In article <1991Jun15.150250.16883@DSI.COM> syd@DSI.COM writes:
>That is a surprise to many of those on NeXT's who are running the
>copy right out of the box with no changes at all.

They're not running 2.0/2.1.  It doesn't link.

>Please note that some of his patches, are personal choices,
>not necessarly bugs.

Which I have so indicated.

>                      And yes, I, have made the decision, not
>to release any more fixes to Elm (unless there is a catastrophic
>problem that causes Elm to loose mail) until the 2.4 release.


>I will note, that he had sent us this patch before for our reference
>and we did look into things in it for the 2.4 release.

Which is still months away.  Some of us like elm, want to run it
now, but are stymied by a distribution that doesn't work.  My
fixes have been tested on a variety of platforms, and have been
in production for several months; they don't break anything, and
they enable some who couldn't otherwise use the package to enjoy
it.  I don't understand your reluctance to maximize elm's
acceptance.  (Tacit NeXT-bashing?)

					-=EPS=-