Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!rutgers!att!cbnewsl!mjs
From: mjs@cbnewsl.ATT.COM (Mike Scheutzow)
Newsgroups: comp.os.minix
Subject: Re: patch to uuencode.c
Keywords: uuencode, uudecode
Message-ID: <2304@cbnewsl.ATT.COM>
Date: 16 Oct 89 23:03:05 GMT
References: <1670@cod.NOSC.MIL>
Organization: AT&T
Lines: 19

> Article 3217 of comp.os.minix:
> 
> This patch substitutes '`' character (0x60) for the space
> charater (0x20) in the output of uuencode.  This is the
> way uuencode on the Navy's Unix system does it.  If you are
> current and already have Terence Holm's patch to uudecode,
> then this change is still compatible with uudecode.

Is someone trying to introduce a change to uuencode/uudecode which is
going to break several years of archived net articles?  Does this mean
that I need to keep different versions of uudecode, depending on when
the file was created?  (I've never noticed a mechanism for uudecode
to decide what version of uuencode encrypted the data.)

Someone please reassure me.  Keeping bitnet happy is one thing, but
adding complications to *my* life is just plain unreasonable. :-)

Mike S.
att!cbnewsl!mjs