57 lines
2.5 KiB
HTML
57 lines
2.5 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
|
<TITLE> The RCS MINI-HOWTO: Overview of RCS.</TITLE>
|
|
<LINK HREF="RCS-2.html" REL=next>
|
|
|
|
<LINK HREF="RCS.html#toc1" REL=contents>
|
|
</HEAD>
|
|
<BODY>
|
|
<A HREF="RCS-2.html">Next</A>
|
|
Previous
|
|
<A HREF="RCS.html#toc1">Contents</A>
|
|
<HR>
|
|
<H2><A NAME="s1">1. Overview of RCS.</A></H2>
|
|
|
|
<P>RCS, the revision control system, is a suite of programs that tracks
|
|
changes in text files and controls shared access to files in work
|
|
group situations. It is generally used to maintain source code
|
|
modules. It lends itself to tracking revisions of document files as
|
|
well.
|
|
<P>RCS was written by Walter F. Tichy and Paul Eggert. The latest
|
|
version which has been ported to Linux is RCS Version 5.7. There is
|
|
also a semi-official, threaded version available. Much of the
|
|
information in this HOWTO is taken from the RCS man pages.
|
|
<P>RCS includes the <CODE>rcs(1)</CODE> program, which controls RCS archive
|
|
file attributes, <CODE>ci(1)</CODE> and <CODE>co(1)</CODE>, which check files
|
|
in and out of RCS archives, <CODE>ident(1)</CODE>, which searches RCS
|
|
archives by keyword identifiers, <CODE>rcsclean(1)</CODE>, a program to
|
|
clean up files that are not being worked on or haven't changed,
|
|
<CODE>rcsdiff(1)</CODE>, which runs <CODE>diff(1)</CODE> to compare the
|
|
revisions, <CODE>rcsmerge(1),</CODE> which merges two RCS branches into a
|
|
single working file, and <CODE>rlog(1),</CODE> which prints RCS log
|
|
messages.
|
|
<P>Files archived by RCS may be text of any format, or binary if the
|
|
<CODE>diff</CODE> program used to generate change files handles 8-bit
|
|
data. Files may optionally include identification strings to aid in
|
|
tracking by <CODE>ident(1)</CODE>. RCS uses the utilities
|
|
<CODE>diff(1)</CODE> and <CODE>diff3(3)</CODE> to generate the change files
|
|
between revisions. A RCS archive consists of the initial revision of
|
|
a file, which is version 1.1, and a series of change files, one for
|
|
each revision. Each time a file is checked out of an archive with
|
|
<CODE>co(1)</CODE>, edited, and checked back into the archive with
|
|
<CODE>ci(1)</CODE>, the version number is increased, for example, to 1.2,
|
|
1.3, 1.4, and so on for successive revisions.
|
|
<P>The archives themselves commonly reside in a <CODE>./RCS</CODE>
|
|
subdirectory, although RCS has other options for archive storage.
|
|
<P>For an overview of RCS, see the <CODE>rcsintro(1)</CODE> manual page.
|
|
<P>
|
|
<P>
|
|
<HR>
|
|
<A HREF="RCS-2.html">Next</A>
|
|
Previous
|
|
<A HREF="RCS.html#toc1">Contents</A>
|
|
</BODY>
|
|
</HTML>
|