Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!ginosko!gem.mps.ohio-state.edu!apple!oliveb!felix!art
From: art@felix.UUCP (Art Dederick)
Newsgroups: comp.sources.d
Subject: Re: rcs for SysV
Message-ID: <118144@felix.UUCP>
Date: 12 Oct 89 19:12:17 GMT
References: <78@vidiot.UUCP> <1367@celit.fps.com> <18167@pasteur.Berkeley.EDU>
Reply-To: art@felix.UUCP (Art Dederick)
Distribution: na
Organization: FileNet Corp., Costa Mesa, CA
Lines: 10

In article <18167@pasteur.Berkeley.EDU> hastings@baobab.Berkeley.EDU (Mark Hastings) writes:
>But we'd become so attached to the features of the sccs front end that RCS
>lacked (sccs info, etc..) that we decided to wait until there was a complete,

I would like to see a list of features you claim is missing from RCS.
I've been using RCS for years and cannot imagine what could be missing.

Art Dederick
felix!art
(714)966-3618