Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Scott Miller — — source: Informix-list mailing list archive (1991-1998)
kerry@kcbbs.gen.nz (Kerry Sainsbury) writes:
>In article <4i1l6o$o8q@cssun.mathcs.emory.edu>,
>m.mejia@server1.codetel.net.do ("=?iso-8859-1?Q?=22Ing._Melvin_P=E9rez_Cedano=22?=" ) wrote:
>>Hello Unix Guru:
>>
>>I would like to hear your opinions about the pros and cons between these two
>>source code control systems.
>>
>>I'm considering to use one of these, but before I would like to know your
>>experiences.
>They're pretty similar really, but RCS makes it easier to produce "patch"
>files.
>*We* use CVS instead. It sits on top of RCS (and is free too!) and provides
>Concurrent editing of programs (ie: more than one person can work on the
>same file at the same time).
>It's excellent. (IMHO).
The O'Reily book _Applying_RCS_and_SCCS_ is a good source of information.
I learned SCCS rather quickly with this book, and it seems to have quite
a lot of information on RCS too. The book seperates the information
presented into 3 categories:
1) Stuff that is general to all source control systems or stuff
that is common to both RCS and SCCS. Also compares pros and
cons of both systems in this category.
2) Stuff specific to RCS.
3) Stuff specific to SCCS.
Great book IMHO.
Scott Miller
--
--
+-----------------------------------------------------------------+
| Scott A. Miller |
| Unix Integration Services scottm@uis.com |
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.