home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 22 gnu
/
22-gnu.zip
/
rcs567x.zip
/
doc
/
rcsfile.man
< prev
next >
Wrap
Text File
|
1994-03-22
|
9KB
|
199 lines
RCSFILE(5) RCSFILE(5)
NNAAMMEE
rcsfile - format of RCS file
DDEESSCCRRIIPPTTIIOONN
An RCS file's contents are described by the grammar below.
The text is free format: space, backspace, tab, newline,
vertical tab, form feed, and carriage return (collec-
tively, _w_h_i_t_e _s_p_a_c_e) have no significance except in
strings. However, white space cannot appear within an id,
num, or sym, and an RCS file must end with a newline.
Strings are enclosed by @@. If a string contains a @@, it
must be doubled; otherwise, strings can contain arbitrary
binary data.
The meta syntax uses the following conventions: `|' (bar)
separates alternatives; `{' and `}' enclose optional
phrases; `{' and `}*' enclose phrases that can be repeated
zero or more times; `{' and '}+' enclose phrases that must
appear at least once and can be repeated; Terminal symbols
are in bboollddffaaccee; nonterminal symbols are in _i_t_a_l_i_c_s.
_r_c_s_t_e_x_t ::= _a_d_m_i_n {_d_e_l_t_a}* _d_e_s_c {_d_e_l_t_a_t_e_x_t}*
_a_d_m_i_n ::= hheeaadd {_n_u_m};;
{ bbrraanncchh {_n_u_m};; }
aacccceessss {_i_d}*;;
ssyymmbboollss {_s_y_m :: _n_u_m}*;;
lloocckkss {_i_d :: _n_u_m}*;; {ssttrriicctt ;;}
{ ccoommmmeenntt {_s_t_r_i_n_g};; }
{ eexxppaanndd {_s_t_r_i_n_g};; }
{ _n_e_w_p_h_r_a_s_e }*
_d_e_l_t_a ::= _n_u_m
ddaattee _n_u_m;;
aauutthhoorr _i_d;;
ssttaattee {_i_d};;
bbrraanncchheess {_n_u_m}*;;
nneexxtt {_n_u_m};;
{ _n_e_w_p_h_r_a_s_e }*
_d_e_s_c ::= ddeesscc _s_t_r_i_n_g
_d_e_l_t_a_t_e_x_t ::= _n_u_m
lloogg _s_t_r_i_n_g
{ _n_e_w_p_h_r_a_s_e }*
tteexxtt _s_t_r_i_n_g
_n_u_m ::= {_d_i_g_i_t | ..}+
_d_i_g_i_t ::= 00 | 11 | 22 | 33 | 44 | 55 | 66 | 77 | 88 | 99
_i_d ::= {_n_u_m} _i_d_c_h_a_r {_i_d_c_h_a_r | _n_u_m}*
GNU 1994/03/17 1
RCSFILE(5) RCSFILE(5)
_s_y_m ::= {_d_i_g_i_t}* _i_d_c_h_a_r {_i_d_c_h_a_r | _d_i_g_i_t}*
_i_d_c_h_a_r ::= any visible graphic character except _s_p_e_c_i_a_l
_s_p_e_c_i_a_l ::= $$ | ,, | .. | :: | ;; | @@
_s_t_r_i_n_g ::= @@{any character, with @@ doubled}*@@
_n_e_w_p_h_r_a_s_e ::= _i_d _w_o_r_d* ;;
_w_o_r_d ::= _i_d | _n_u_m | _s_t_r_i_n_g | ::
Identifiers are case sensitive. Keywords are in lower
case only. The sets of keywords and identifiers can over-
lap. In most environments RCS uses the ISO 8859/1 encod-
ing: visible graphic characters are codes 041-176 and
240-377, and white space characters are codes 010-015 and
040.
Dates, which appear after the ddaattee keyword, are of the
form _Y.._m_m.._d_d.._h_h.._m_m.._s_s, where _Y is the year, _m_m the month
(01-12), _d_d the day (00-31), _h_h the hour (00-23), _m_m the
minute (00-59), and _s_s the second (00-60). _Y contains
just the last two digits of the year for years from 1900
through 1999, and all the digits of years thereafter.
Dates use the Gregorian calendar; times use UTC.
The _n_e_w_p_h_r_a_s_e productions in the grammar are reserved for
future extensions to the format of RCS files. No _n_e_w_-
_p_h_r_a_s_e will begin with any keyword already in use.
The _d_e_l_t_a nodes form a tree. All nodes whose numbers con-
sist of a single pair (e.g., 2.3, 2.1, 1.3, etc.) are on
the trunk, and are linked through the nneexxtt field in order
of decreasing numbers. The hheeaadd field in the _a_d_m_i_n node
points to the head of that sequence (i.e., contains the
highest pair). The bbrraanncchh node in the admin node indi-
cates the default branch (or revision) for most RCS opera-
tions. If empty, the default branch is the highest branch
on the trunk.
All _d_e_l_t_a nodes whose numbers consist of 2_n fields (_n>=2)
(e.g., 3.1.1.1, 2.1.2.2, etc.) are linked as follows.
All nodes whose first 2_n-1 number fields are identical are
linked through the nneexxtt field in order of increasing num-
bers. For each such sequence, the _d_e_l_t_a node whose number
is identical to the first 2_n-2 number fields of the deltas
on that sequence is called the branchpoint. The bbrraanncchheess
field of a node contains a list of the numbers of the
first nodes of all sequences for which it is a branch-
point. This list is ordered in increasing numbers.
The following diagram shows an example of an RCS file's
organization.
GNU 1994/03/17 2
RCSFILE(5) RCSFILE(5)
Head
|
|
v / \
--------- / \
/ \ / \ | | / \ / \
/ \ / \ | 2.1 | / \ / \
/ \ / \ | | / \ / \
/1.2.1.3\ /1.3.1.1\ | | /1.2.2.2\ /1.2.2.1.1.1\
--------- --------- --------- --------- -------------
^ ^ | ^ ^
| | | | |
| | v | |
/ \ | --------- / \ |
/ \ | \ 1.3 / / \ |
/ \ ---------\ / / \-----------
/1.2.1.1\ \ / /1.2.2.1\
--------- \ / ---------
^ | ^
| | |
| v |
| --------- |
| \ 1.2 / |
----------------------\ /---------
\ /
\ /
|
|
v
---------
\ 1.1 /
\ /
\ /
\ /
IIDDEENNTTIIFFIICCAATTIIOONN
Author: Walter F. Tichy, Purdue University, West
Lafayette, IN, 47907.
Revision Number: 5.5; Release Date: 1994/03/17.
Copyright (C) 1982, 1988, 1989 Walter F. Tichy.
Copyright (C) 1990, 1991, 1992, 1993, 1994 Paul Eggert.
SSEEEE AALLSSOO
rcsintro(1), ci(1), co(1), ident(1), rcs(1), rcsclean(1),
rcsdiff(1), rcsmerge(1), rlog(1)
Walter F. Tichy, RCS--A System for Version Control,
_S_o_f_t_w_a_r_e_-_-_P_r_a_c_t_i_c_e _& _E_x_p_e_r_i_e_n_c_e 1155, 7 (July 1985),
637-654.
GNU 1994/03/17 3