Scribd Logo
Upload

Welcome to Scribd!

  • 35 views

    Rcs Document Part2

    Uploaded by

    rajesh.remaraghavan1866
    RCS (Revision Control System) manages multiple revisions of files and allows users to store, retrieve, log, identify, and merge revisions. It was designed by Walter F. Tichy and supports text and binary files. Common commands for RCS include ci, co, ident, merge, rcs, rcsclean, rcsdiff, and rcsmerge. The document then provides credits for contributors to different versions of RCS and introduces some basic concepts of RCS including its interaction model of initializing an RCS file and then checking out, modifying, and checking in files.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Rcs Document Part2

    Uploaded by

    rajesh.remaraghavan1866
    35 views1 page
    RCS (Revision Control System) manages multiple revisions of files and allows users to store, retrieve, log, identify, and merge revisions. It was designed by Walter F. Tichy and supports text and binary files. Common commands for RCS include ci, co, ident, merge, rcs, rcsclean, rcsdiff, and rcsmerge. The document then provides credits for contributors to different versions of RCS and introduces some basic concepts of RCS including its interaction model of initializing an RCS file and then checking out, modifying, and checking in files.

    Original Title

    rcs-document-part2

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    RCS (Revision Control System) manages multiple revisions of files and allows users to store, retrieve, log, identify, and merge revisions. It was designed by Walter F. Tichy and supports text and binary files. Common commands for RCS include ci, co, ident, merge, rcs, rcsclean, rcsdiff, and rcsmerge. The document then provides credits for contributors to different versions of RCS and introduces some basic concepts of RCS including its interaction model of initializing an RCS file and then checking out, modifying, and checking in files.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    35 views1 page

    Rcs Document Part2

    Uploaded by

    rajesh.remaraghavan1866
    RCS (Revision Control System) manages multiple revisions of files and allows users to store, retrieve, log, identify, and merge revisions. It was designed by Walter F. Tichy and supports text and binary files. Common commands for RCS include ci, co, ident, merge, rcs, rcsclean, rcsdiff, and rcsmerge. The document then provides credits for contributors to different versions of RCS and introduces some basic concepts of RCS including its interaction model of initializing an RCS file and then checking out, modifying, and checking in files.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 1

    Chapter 1: Overview 1

    1 Overview
    GNU RCS (Revision Control System) manages multiple revisions of files. RCS can store,
    retrieve, log, identify, and merge revisions. It is useful for files that are revised frequently,
    e.g. programs, documentation, graphics, and papers. It can handle text as well as binary
    files, although functionality is reduced for the latter.
    A normal installation includes the commands: ci, co, ident, merge, rcs, rcsclean, rcsdiff,
    rcsmerge and rlog (see Chapter 2 [Usage], page 7). These are small and fast programs
    (amenable to scripting) and indeed the distribution also includes the script rcsfreeze showing
    some of the possibilities.
    RCS works with versions stored on a single filesystem or machine, edited by one person at
    a time. Other version control systems, such as Bazaar (http:///www.gnu.org/software/
    bazaar), CVS, Subversion, and Git, support distributed access in various ways. Which is
    more appropriate depends on the task at hand.

    1.1 Credits
    RCS was designed and built by Walter F. Tichy of Purdue University. RCS version 3 was
    released in 1983.
    Adam Hammer, Thomas Narten, and Daniel Trinkle of Purdue supported RCS through
    version 4.3, released in 1990. Guy Harris of Sun contributed many porting fixes. Paul
    Eggert of System Development Corporation contributed bug fixes and tuneups. Jay Lepreau
    contributed 4.3BSD support.
    Paul Eggert of Twin Sun wrote the changes for RCS versions 5.5 and 5.6 (1991). Rich
    Braun of Kronos and Andy Glew of Intel contributed ideas for new options. Bill Hahn of
    Stratus contributed ideas for setuid support. Ideas for piece tables came from Joe Berkovitz
    of Stratus and Walter F. Tichy. Matt Cross of Stratus contributed test case ideas. Adam
    Hammer of Purdue QAed.
    Paul Eggert wrote most of the changes for RCS 5.7. K. Richard Pixley of Cygnus Support
    contributed several bug fixes. Robert Lupton of Princeton and Daniel Trinkle contributed
    ideas for ‘$Name’ expansion. Brendan Kehoe of Cygnus Support suggested rlog’s -N option.
    Paul D. Smith of Data General suggested improvements in option and error processing.
    Adam Hammer of Purdue QAed.
    Thien-Thi Nguyen is responsibile for RCS 5.8. He modernized the code base, build sys-
    tem, and manual pages, fixing some bugs on the way. He added standard --help, --version
    processing, and wrote the documentation you are reading (gladly taking inspiration from
    the paper1 and manpages originally written by Walter F. Tichy).

    1.2 Concepts
    1.2.1 Interaction model
    The interaction model is straightforward. For each working file, you initialize its RCS file
    once, then enter a cycle of checkout, modification, and checkin operations. Along the way,
    1
    Source (troff) and several output formats are available from the RCS homepage (http://www.gnu.org/
    software/rcs/).

    You might also like