Scribd
Upload
32 views1 page

2 Usage: 2.1 Common Elements

This chapter describes how to invoke RCS commands and common elements across commands. RCS commands take the form of a hyphen followed by a single letter option, followed by optional extra information. Options must come before file names and files can be specified individually or as pairs. Revision options often take the form of -flag[rev] where rev defaults to the latest if omitted and can be specified in various ways like branch.number, name or by examining keyword expansions.

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
32 views1 page

2 Usage: 2.1 Common Elements

This chapter describes how to invoke RCS commands and common elements across commands. RCS commands take the form of a hyphen followed by a single letter option, followed by optional extra information. Options must come before file names and files can be specified individually or as pairs. Revision options often take the form of -flag[rev] where rev defaults to the latest if omitted and can be specified in various ways like branch.number, name or by examining keyword expansions.

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 2: Usage 7

2 Usage

This chapter describes how to invoke RCS commands, including common command-line
elements, as well options specific to each command.

2.1 Common elements


All RCS commands accept --help and --version. See Section “Command-Line Interfaces”
in The GNU Coding Standards.
Aside from --help and --version, RCS commands take the form ‘-letter[arg]’, i.e.,
a hyphen followed by a single letter, optionally followed by extra information. The square
braces mean that the extra information is optional. (No square braces means that the extra
information is required.) In any case, when specified, the extra information must abut the
letter; there can be no intervening whitespace.
co -u 1.4 foo # wrong, space between -u and 1.4
co -u1.4 foo # ok
Furthermore, options must appear before file names (if any) on the command line.
ident foo -q # wrong, option after file name
ident -q foo # ok
Lastly, pairs of RCS and working files can be specified in three ways: (a) both are given, (b)
only the working file is given, (c) only the RCS file is given. For (a), both RCS and working
files may have arbitrary directory components; RCS commands pair them up intelligently.
For (b), RCS commands will look first into the directory ./RCS, if it exists, to find the
associated RCS file.

2.1.1 Revision options


As to be expected in a revision control system, many options are of the form ‘-flag[rev]’,
where flag is a single letter (e.g., ‘r’). If ommitted, rev defaults to the latest revision on
the default branch. A revision can be specified in many ways:

br.n Straightforward dot-notation, where br specifies the branch.


.n Like br.n, using the default branch.
br Like br.n, using the a command-specific computation of n, given the current
tip i. For ci (see Section 2.2 [ci], page 11), n would be i + 1, while for other
commands n would be simply i.
name This is the symbolic name of a revision, as assigned previously by a ci -n or
ci -N command.
$ The command computes the effective revision by examining the values of key-
word expansions in the working file.

For commands that accept a range of revisions, the syntax is generally rev1:rev2, i.e., two
revisions (specified as described above) separated by a colon.

You might also like