Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!eru!luth!sunic!mcsun!inria!laas!news
From: news@laas.laas.fr (USENET News System)
Newsgroups: news.software.b
Subject: Re: rn/rrn patchlevels, etc.
Summary: Let's post patchs to comp.sources.bugs!
Keywords: rn, rrn, patchs
Message-ID: <457@laas.laas.fr>
Date: 24 Oct 89 10:04:43 GMT
References: <47.filbo@gorn.santa-cruz.ca.us> <54.filbo@gorn.santa-cruz.ca.us> <10049@ucsd.Edu>
Reply-To: ralph@laas.laas.fr	(Ralph P. Sobek)
Organization: LAAS-CNRS, Toulouse, France
Lines: 31

In article <10049@ucsd.Edu> brian@ucsd.edu (Brian Kantor) writes:
|  The author of 'rn', Larry Wall, has publicly stated that he isn't going
|  to do any more work on 'rn'.

Thanks Larry, for rn!

|  In the meantime, I know of no one collecting patches or taking
|  maintenance responsibility for 'rn'.  It is essentially a mature
|  product with a few minor bugs.  Or maybe you can consider it an orphan,
|  if that makes you feel better.
|  
|  I suspect that if you were to publish bugfixes in comp.sources.bugs, or
|  put them out somewhere for FTP retrieval, people would be grateful.  

I assume that there are many sites that run rn/rrn.  If so, we should
post patchs to rn/rrn in comp.sources.bugs in order to iron out those
"minor bugs."  I've found a number for rrn's script files: basically
annoyances that can be gotten around, but why reinvent the wheel each
and every time.

Cheers to all,




Ralph P. Sobek			  Disclaimer: The above ruminations are my own.
ralph@laas.laas.fr			   Addresses are ordered by importance.
ralph@laas.uucp, or ...!uunet!mcvax!laas!ralph		If all else fails, try:
SOBEK@FRMOP11.BITNET				      sobek@eclair.Berkeley.EDU
===============================================================================
Upon the instruments of death the sunlight brightly gleams.   --   King Crimson