eggert@dew.uucp (Paul Eggert) (05/07/90)
From: uunet!twinsun!dew!eggert (Paul Eggert)
In comp.std.unix 19:96 hlj@posix.COM (Hal Jespersen) writes:
The group was overwhelmingly in favor of using SCCS as the superior
technical solution, but SCCS has two problems:
Could someone in the group summarize why the group decided that SCCS is
superior technically? Tichy's paper on RCS says that it is usually faster than
SCCS. In my spare time, I'm preparing several improvements to RCS that I'll
eventually submit to Purdue, and if there are easy ways to improve RCS I'd like
to hear about them.
Volume-Number: Volume 19, Number 107ghoti+@andrew.cmu.edu (Adam Stoller) (05/08/90)
From: Adam Stoller <ghoti+@andrew.cmu.edu> Excerpts from comp.std.unix: 6-May-90 Advantages of SCCS? Paul Eggert@dew.uucp > I'm preparing several improvements to RCS that I'll eventually submit to > Purdue, and if there are easy ways to improve RCS I'd like to hear about them. There's a package called CVS which is a front-end for RCS that allows for parallel development. It has several very nice features. It was just recently posted to comp.sources.unix (I think) --fish Volume-Number: Volume 19, Number 111
stevedc@syma.sussex.ac.uk (Stephen Carter) (05/08/90)
From: Stephen Carter <stevedc@syma.sussex.ac.uk> >From article <672@longway.TIC.COM>, by eggert@dew.uucp (Paul Eggert): > From: uunet!twinsun!dew!eggert (Paul Eggert) > > In comp.std.unix 19:96 hlj@posix.COM (Hal Jespersen) writes: > > The group was overwhelmingly in favor of using SCCS as the superior > technical solution, but SCCS has two problems: > > Could someone in the group summarize why the group decided that SCCS is > superior technically? Tichy's paper on RCS says that it is usually faster than etc... Agreed. Could I second Paul's request for elaboration of this one. Everything I have read has indicated that RCS is better, so I was going to go for it - but I would rather be with the 'future proof' facility. Ta. Stephen Carter, Systems Manager, The Administration, The University of Sussex, Falmer, Brighton BN1 9RH, UK Tel: +44 273 678203 Fax: +44 273 678335 JANET: stevedc@uk.ac.sussex.syma EARN/BITNET : stevedc@syma.sussex.ac.uk UUCP: stevedc@syma.uucp ARPA/INTERNET: stevedc%syma.sussex.ac.uk@nsfnet-relay.ac.uk Volume-Number: Volume 19, Number 110
matt@bacchus.oz.au (Matthew Atterbury) (05/09/90)
From: matt@bacchus.oz.au (Matthew Atterbury) In article <672@longway.TIC.COM> you write: > ... In my spare time, I'm preparing several improvements to RCS that I'll >eventually submit to Purdue, and if there are easy ways to improve RCS I'd >like to hear about them. Our company has two sites working on the same code. We create patch files to distribute our local changes to the remote site. I have had to hack up a shell script for rcsdiff (doing it all by hand) s.t. $keyword differences are ignored (since our $Source$, $Header$, and $Log$ expansions are usually slightly different). A switch to rcsdiff which somehow ignored such differences would be nice. A "good" way would be for the $Log$ entries never to be expanded in the ,v file, but built up everytime you co'd the file. A switch to co would *not* expand keywords - thus, rcsdiff could co the two versions to be diff'd with this switch set and do a diff on them. Clearly such diff's should be applied to a similarly co'd file - perhaps a command/method to convert expanded $keyword's to their unexpanded versions would handle this and the rcsdiff "problem". Obviously $Log$ is the tricky one since it is multi-line and not clearly delineated - I have handled it by assuming that ALL lines following $Log which start with the $Log prefix + a space (eg. " * " or "# ") are $Log lines - works OK for us. Apart from this, I too prefer RCS to SCCS (not that SCCS would necessarily be any better than RCS in this regard!). cheers ... -- ------------------------------------------------------------------------------- Matt Atterbury [matt@bacchus.esa.oz.au] Expert Solutions Australia, Melbourne UUCP: ...!uunet!munnari!matt@bacchus.esa.oz.au "klaatu barada nikto" ARPA: matt%bacchus.esa.oz.AU@uunet.UU.NET "life? don't talk to me about life!" Volume-Number: Volume 19, Number 112