Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!sri-unix!husc6!bloom-beacon!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!hplabs!hpda!hpesoc1!hpcllla!hpclisp!hpclskh!skh From: skh@hpclskh.HP.COM Newsgroups: comp.unix.questions Subject: SCCS vs. RCS Message-ID: <720003@hpclskh.HP.COM> Date: 12 Jan 88 22:53:04 GMT References: <743@dragon.UUCP> Organization: HP ITG/ISO Computer Language Lab Lines: 43 / hpclskh:comp.unix.questions / robf2@pyuxf.UUCP (robert fair) / 6:43 am Dec 16, 1987 / In article <1987Dec9.235431.11368@gpu.utcs.toronto.edu>, poetry@utgpu.UUCP writes: > > In article <743@dragon.UUCP> charles@dragon.UUCP (Charles Wolff, x3432) writes: > >I'm involved in a project which is going to have a fairly large source > >code base, and we're currently in the process of deciding whether to > >use sccs or rcs for source code control. Would like to hear from anyone > >who: > > > > 1) is familiar with both SCCS and RCS. _AND_ > > > > 2) can give me examples of things that they are doing with one > > that couldn't be done with the other. > > > >Thanks in advance... > > > I would love to hear about this, too. Thanks. Me, Three. Thanks Poster Filler Poster Filler Poster Filler Poster Filler Poster Filler Poster Filler ---------- My only comment to you would be this: the versions of SCCS I have seen store the original source file and differences from that file. RCS versions tend to store the latest source file and differences from previous versions. This means that SCCS takes longer to give the the latest version of a file; RCS takes longer to get back to a previous version. When I am in program development, I find it much easier to have fast access to the most recent version of a file. I find that I need older versions much less often, and I am willing to wait. Naturally, if you think you will be working on older versions more often (such as after a product release), SCCS may be a better choice. Instant disclaimer: Not all versions of SCCS and RCS have this property. Disclaimer #2: No other comments about ease of use. skh