Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!husc6!yale!mfci!bronson From: bronson@mfci.UUCP (Tan Bronson) Newsgroups: comp.sources.d Subject: Re: rcs for SysV Message-ID: <1083@m3.mfci.UUCP> Date: 16 Oct 89 15:13:09 GMT References: <78@vidiot.UUCP> <1367@celit.fps.com> <18167@pasteur.Berkeley.EDU> <118144@felix.UUCP> Sender: news@mfci.UUCP Reply-To: bronson@mfci.UUCP (Tan Bronson) Distribution: na Organization: Multiflow Computer Inc., Branford Ct. 06405 Lines: 25 >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 I've spent a fair number of years hacking RCS to write higher level tools, and while I tend to agree that RCS is very complete. I've added: rlog -H (dump revision number of the header) rlog -S (dump revision number of symbol) rcs -B break a lock and send mail One tool I'd love to see is a graphical display of the branch structure of a RCS file. I'm starting to use branches now much more and I'm worried that someday I'll hit a limit... I'd also like to see a clean subroutine library to access RCS files. (I've got code which reads symbols + locks from an RCS file) Tan Bronson Multiflow Computer Inc UUCP(work): {yale,uunet}!mfci!bronson 30 Business Park UUCP(home): {yale,mfci}!bronson!tan Branford, Ct 06405 Phone(work):(203)-488-6090