Return to README CVS log

Up to [CSRG BSD Unix] / 43BSD / contrib / rcs

Annotation of 43BSD/contrib/rcs/README, revision 1.1

1.1     ! root        1: Title:         RCS Revision Control System
        !             2: 
        !             3: Author:                Walter F. Tichy
        !             4: 
        !             5: Address:       Department of Computer Sciences
        !             6:                Purdue University
        !             7:                West Lafayette, IN 47907
        !             8: 
        !             9: Net address:   wft@purdue      (ARPA)
        !            10: 
        !            11: Description:
        !            12: 
        !            13: The Revision Control System (RCS) manages multiple revisions of text files.
        !            14: RCS automates the storing, retrieval, logging, identification, and merging
        !            15: of revisions. RCS is useful for text that is revised frequently, for example
        !            16: programs, documentation, graphics, papers, form letters, etc.
        !            17: 
        !            18: The sccstorcs command was added in 4.3BSD:
        !            19: 
        !            20: Title:         sccstorcs
        !            21: 
        !            22: Author:                Kenneth L. Greer
        !            23:                2065 Alma St.
        !            24:                Palo Alto, CA 94301
        !            25: 
        !            26: Net address:   kg.HP-Labs@Rand-Relay
        !            27: 
        !            28: Description:
        !            29: 
        !            30: Sccstorcs builds an RCS Revision Control System file from an SCCS
        !            31: Source Code Control System file. The deltas and comments for each
        !            32: delta are preserved and installed into the new RCS file in order.
        !            33: Also preserved are the user access list and descriptive text, if
        !            34: any, from the SCCS file.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.