Path: utzoo!attcan!uunet!mcsun!ukc!pyrltd!slxsys!ibmpcug!ronald
From: ronald@ibmpcug.co.uk (Ronald Khoo)
Newsgroups: news.software.b
Subject: Re: 14-Sep-1989 patch for C News
Message-ID: <224f.2511f7ff@ibmpcug.co.uk>
Date: 16 Sep 89 07:36:31 GMT
References: <1989Sep14.200112.6029@utzoo.uucp>
Reply-To: Ronald.Khoo@ibmpcug.CO.UK
Organization: The IBM PC User Group, UK.
Lines: 32

*** C News alert -- B News users hit 'n' NOW! *** <<-- C News don't need
						       no bug fodder :-)

In article <1989Sep14.200112.6029@utzoo.uucp> Henry Spencer writes:
>*** cnpatch/tmp.file	Thu Sep 14 15:54:41 1989
>--- relay/regress/out/stderr	Wed Sep 13 20:35:17 1989

I got a problem with this one. It seems to want on of these:
*** cnpatch/tmp.preposterously.long.name.to.make.patch.behave.right	
or it screws up itself and the next patch.

[ for those not 'in the know', evidence of this screwup is the existence
  of the directory 'cnpatch' after patching ]

I built the 24 Aug version from the (revised, patched) c.s.u. shars
and applied patches 2-5 (oops sorry, I mean, er, 7-Jul, etc.. er..
you know what I mean :-) to get the 24 Aug version to patch and it still
happened.

Can someone explain the original patch bogosity anyway? thanks...

>(suggested archive name: `pch14Sep89.Z')
err.. that makes the collating order inconvenient..  It would be
nice if the shell globbed the patch names in order.  How about pch89.09.14 ?
You *could* do what I do (call it patch.6) but... naahh.. too radical :-)

'ave a nice day y'all.....

-- 
Ronald.Khoo@ibmpcug.CO.UK (The IBM PC User Group, PO Box 360, Harrow HA1 4LQ)
Path: ...!ukc!slxsys!ibmpcug!ronald Phone: +44-1-863 1191 Fax: +44-1-863 6095
$Header: /users/ronald/.signature,v 1.1 89/09/03 23:36:16 ronald Exp $ :-)