Scribd
Upload
25 views

Rcs Document Part6

The document discusses the log message stored during check-in to RCS, which includes information like the file name, revision number, author, and date. It also discusses other keywords stored in RCS like the file name, revision number, and state. It then provides a quick overview of common RCS commands like check-in (ci) and check-out (co).

Uploaded by

rajesh.remaraghavan1866
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
25 views

Rcs Document Part6

The document discusses the log message stored during check-in to RCS, which includes information like the file name, revision number, author, and date. It also discusses other keywords stored in RCS like the file name, revision number, and state. It then provides a quick overview of common RCS commands like check-in (ci) and check-out (co).

Uploaded by

rajesh.remaraghavan1866
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Chapter 1: Overview 4

Log The log message supplied during checkin, preceded by a header containing the
RCS filename, the revision number, the author, and the date and time. May
include an appended timezone offset.
Existing log messages are not replaced. Instead, the new log message is inserted
after ‘$Log:...$’. This is useful for accumulating a complete change log in a
source file.
Each inserted line is prefixed by the string that prefixes the ‘$Log$’ line. For
example, if the ‘$Log$’ line is
// $Log: tan.cc $
then RCS prefixes each line of the log with ‘// ’ (slash, slash, space). This is
useful for languages with comments that go to the end of the line.
The convention for other languages is to use a ‘ * ’ (space, asterisk, space)
prefix inside a multiline comment. For example, the initial log comment of a C
program conventionally is of the following form:
/*
* $Log$
*/
For backwards compatibility with older versions of RCS, if the log prefix is ‘/*’
or ‘(*’ surrounded by optional white space, inserted log lines contain a space
instead of ‘/’ or ‘(’; however, this usage is obsolescent and should not be relied
on.
Name The symbolic name used to check out the revision, if any. For example, ‘co
-rJoe’ generates ‘$Name: Joe $’. Plain co generates just ‘$Name: $’.
RCSfile The basename of the RCS file.
Revision The revision number assigned to the revision.
Source The absolute RCS filename.
State The state assigned to the revision with the -s option of rcs or ci.

1.3 Quick tour


This section complements the preceding section (see Section 1.2 [Concepts], page 1), pre-
senting a handful of RCS commands in quick succession. For details on individual RCS
commands, See Chapter 2 [Usage], page 7.
Suppose you have a file f.c that you wish to put under control of RCS. If you have not
already done so, make an RCS directory with the command:
mkdir RCS
Then invoke the checkin command:
ci f.c
This command creates an RCS file in directory RCS, stores f.c into it as revision 1.1, and
deletes f.c. It also asks you for a description. The description should be a synopsis of the
contents of the file. All later checkin commands will ask you for a log entry, which should
summarize the changes that you made.
To get back the working file f.c in the previous example, use the checkout command:

You might also like