Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!shinobu!odin!giraffe!pj From: pj@giraffe.sgi.com (Paul Jackson) Newsgroups: comp.sys.sgi Subject: Re: RCS question Message-ID: <1991Feb13.230332.4620@odin.corp.sgi.com> Date: 13 Feb 91 23:03:32 GMT References: <1991Feb10.180859.7764@cunixf.cc.columbia.edu> Sender: news@odin.corp.sgi.com (Net News) Organization: Silicon Graphics, Inc., Mountain View, CA Lines: 28 shenkin@cunixf.cc.columbia.edu (Peter S. Shenkin) writes: > rcsdiff error, line 2: Missing access list > rcsdiff aborted >I believe this is an RCS version incompatibility ... srp@babar.mmwb.ucsf.edu (Scott R. Presnell) writes: >Yes, I understand that to be correct. Yes, there is an RCS incompatibility. SGI ships a version 3.x RCS. Versions 4.x of RCS are common in some other environments, and have an incompatibility with 3.x versions - a default branch feature was added, including a "branch X.X;" line. The "access" list that used to be on line 2 of the ,v file was pushed down to line 3, causing the above error message. You can "fix" 4.x created ,v files to be read by 3.x based RCS commands by removing this "branch ..." line (it's line 2 of the ,v file). SGI's present plans are to support 4.3 RCS in some future major software release. There are no plans at present for versions 5.5 or higher of RCS, but hopefully, someday, that too will happen. I won't rest till it's the best ... Software Production Engineer Paul Jackson (pj@asd.sgi.com), x1373