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.
Philip Walden — — source: Informix-list mailing list archive (1991-1998)
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.
>
I have used both RCS and SCCS. I favor RCS for probably not very clear
reasons.
- Both RCS and SCCS store changes as incremental edits to and original.
SCCS stores changes from the original version. RCS stores the current
version and the edits back to the original. Thus RCS will always be faster
to retrieve the lastest versions. Also in the rare case that the diff
edits to not apply correctly, at least you current version is not
mangled.
- I believe RCS handles branch and merge better.
- RCS provides for symbolic stamps on versions. We use this feature
extensively
to align the versions on thousands of files into one release of a product.
--
--------------------------------------------------------------------------
Philip Walden
Hewlett Packard
Product Generation Information Systems
1501 Page Mill Road, M/S 4U-6
Palo Alto, CA 94304
(415) 857-3899 FAX (415) 857-8234
--------------------------------------------------------------------------
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.