Date: Tue, 19 Sep 1995 16:23:31 +0400 (MSD) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su> To: Satoshi Asami <asami@cs.berkeley.edu> Cc: CVS-commiters@freebsd.org, cvs-sbin@freebsd.org Subject: Re: cvs commit: src/sbin/startslip startslip.c uucplock.c Message-ID: <fB3PhNmC64@ache.dialup.demos.ru> In-Reply-To: <199509191117.EAA01855@silvia.HIP.Berkeley.EDU>; from Satoshi Asami at Tue, 19 Sep 1995 04:17:58 -0700 References: <199509191117.EAA01855@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199509191117.EAA01855@silvia.HIP.Berkeley.EDU> Satoshi
Asami writes:
> * Modified: sbin/startslip startslip.c uucplock.c
>Gosh, this file (startslip.c) has accumulated 12 revisions in the last
>week. Don't want to sound like a repository janitor, but can you
>please test your changes extensively on your local machine before you
>commit them so that you don't have to come back on the next day (on
>even during the same day) and fix it again?
Sorry, to many things to patch at once (startslip only small visible
edge). Changes involved startslip/slattach/sliplogin/uucp/kermit/etc.
I can't hold all changes in my head (or local copy)
without putting down some milestones (I don't have local CVS copy).
Moreover startslip tricked me because it promise (in comments
and manpages) to do things that really can't. So, trusting to it
first I becomes involved into unexpected work.
--
Andrey A. Chernov : And I rest so composedly, /Now, in my bed,
ache@astral.msk.su : That any beholder /Might fancy me dead -
FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead.
RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fB3PhNmC64>