-->

Previous | Table of Contents | Next

Page 1181

This file might be distributed over a network using a network-wide naming service such as Yellow Pages/NIS or BIND/Hesoid.

FILES

/etc/protocols The protocols definition file.

SEE ALSO

getprotoent(3), Guide to Yellow Pages Service, Guide to BIND/Hesiod Service

Linux, 18 October 1995

rcsfile

rcsfile—Format of RCS file.

DESCRIPTION

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 (collectively, whitespace) have no significance except in strings. However, whitespace 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 boldface; non-terminal symbols are in italics.


rcstext ::= admin {delta}* desc {deltatext}*

       admin ::= head {num};

                 { branch {num}; }

                 access {id}*;

                 symbols {sym : num}*;

                 locks {id : num}*; {strict ;}



                 { comment {string}; }

                 { expand {string}; }

                 { newphrase }*

       delta ::= num

                 date num;

                 author id;

                 state {id};

                 branches {num}*;

                 next {num};

                 { new-phrase }*

       desc ::=  desc string

       deltatext ::= num

                     log string

                     { newphrase }*

                     text string

       num ::= {digit | .}+

       digit ::= 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9

       id ::= {num} idchar {idchar | num}*

       sym ::= {digit}* idchar {idchar | digit}*

       idchar ::= any visible graphic character except special

       special ::= $ | , | . | : | ; | @

       string ::= @{any character, with @doubled}*@

Page 1182


       newphrase ::= id word* ;

       word ::= id | num | string | :

Identifiers are case sensitive. Keywords are in lowercase only. The sets of keywords and identifiers can overlap. In most environments, RCS uses the ISO8859/1 encoding: visible graphic characters are codes 041_176 and 240_377, and whitespace characters are codes 010_015 and 040.

Dates, which appear after the date keyword, are of the form Y.mm.dd.hh.mm.ss, where Y is the year, mm the month (01_12), dd the day (01_31), hh the hour (00_23), mm the minute (00_59), and ss 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 newphrase productions in the grammar are reserved for future extensions to the format of RCS files. No newphrase will begin with any keyword already in use.

The delta nodes form a tree. All nodes whose numbers consist of a single pair (such as 2.3, 2.1, 1.3, and so on) are on the trunk and are linked through the next field in order of decreasing numbers. The head field in the admin node points to the head of that sequence (contains the highest pair). The branch node in the admin node indicates the default branch (or revision) for most RCS operations. If empty, the default branch is the highest branch on the trunk.

All delta nodes whose numbers consist of 2n fields (n2) (such as 3.1.1.1, 2.1.2.2, and so on) are linked as follows. All nodes whose first 2n_1 number fields are identical are linked through the next field in order of increasing numbers. For each such sequence, the delta node whose number is identical to the first 2n_2 number fields of the deltas on that sequence is called the branchpoint. The branches field of a node contains a list of the numbers of the first nodes of all sequences for which it is a branchpoint. This list is ordered in increasing numbers.

The following diagram shows an example of an RCS file's organization.


                               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  /

                              \     /

                               \   /

                                \ /



Previous | Table of Contents | Next