Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!ucsdhub!hp-sdd!ncr-sd!ncrlnk!rd1632!hann
From: hann@rd1632.Dayton.NCR.COM (Ed Hann)
Newsgroups: comp.mail.elm
Subject: Re: Future Elm patches
Keywords: patches code elm
Message-ID: <472@rd1632.Dayton.NCR.COM>
Date: 14 Jun 88 19:00:25 GMT
References: <1095@bellboy.UUCP> <419@altnet.ALTOS.COM> <144@ists>
Reply-To: hann@rd1632.Dayton.NCR.COM (Ed Hann)
Organization: R&D, NCR Corp., Dayton, Ohio
Lines: 26

In article <144@ists> mike@ists.yorku.ca (Mike Clarkson) writes:
>
>Everyone can post comments and patches here, and periodically the coordinator
>can post official patches.

Perhaps the coordinator could collect the unofficial patches, store them in
there original posting form for anybody to retrieve via uucp.  He could
maintain original code and official patches separately, also available for
retrieval via uucp.  He could periodically post info on where to get them in
case a user misses an original posting or to help new readers.  All code:
original, unofficial patches, and official patches; is always available to
anybody via uucp.

>> Additionally, let's set up a mailing list of some sort for the testers and 
>> developers. That way we can ensure that everybody knows what's going on 
>> all the time. The "pre-test" patches could be mailed to the testers and
>> developers also.
>

Good idea, if it would help the coordinator keep the testers together.


Ed Hann					(Ed.Hann@Dayton.NCR.COM)
Applied Research, R&D Division 			or
NCR Corp., World Headquarters, 5/E	(Ed.Hann%Dayton.NCR.COM@RELAY.CS.NET)
Dayton, Ohio 45479
513 445-1061