SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG

BotDetect - Real-Time Bot Detection API
 
 

MAN page from Mandrake Other rcs-5.7-7.i386.rpm

RCSFILE

Section: File Formats (5)
Updated: 1995/06/05
Index 

NAME

rcsfile - format of RCS file 

DESCRIPTION

An RCS file'scontents are described by the grammarbelow.

The text is free format: space, backspace, tab, newline, verticaltab, form feed, and carriage return (collectively,white space)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) separatesalternatives; `{' and `}' enclose optional phrases; `{' and `}*' enclosephrases that can be repeated zero or more times;`{' and '}+' enclose phrases that must appear at least once and can berepeated;Terminal symbols are inboldface;nonterminal symbols are initalics.

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};                 { newphrase }*desc        ::=  desc         stringdeltatext   ::=  num                 log          string                 { newphrase }*                 text         stringnum         ::=  {digit | .}+digit       ::=  0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9id          ::=  {num} idchar {idchar | num}*sym         ::=  {digit}* idchar {idchar | digit}*idchar      ::=  any visible graphic character except specialspecial     ::=  $ | , | . | : | ; | @string      ::=  @{any character, with @ doubled}*@newphrase   ::=  id word* ;word        ::=  id | num | string | :

Identifiers are case sensitive. Keywords are in lower case only.The sets of keywords and identifiers can overlap.In most environments RCS uses the ISO 8859/1 encoding:visible graphic characters are codes 041-176 and 240-377,and white space characters are codes 010-015 and 040.

Dates, which appear after thedatekeyword, are of the formY.mm.dd.hh.mm.ss,whereYis the year,mmthe month (01-12),ddthe day (01-31),hhthe hour (00-23),mmthe minute (00-59),andssthe second (00-60).Ycontains just the last two digits of the yearfor years from 1900 through 1999,and all the digits of years thereafter.Dates use the Gregorian calendar; times use UTC.

Thenewphraseproductions in the grammar are reserved for future extensionsto the format of RCS files.Nonewphrasewill begin with any keyword already in use.

Thedeltanodes form a tree. All nodes whose numbersconsist of a single pair(e.g., 2.3, 2.1, 1.3, etc.)are on the trunk, and are linked through thenextfield in order of decreasing numbers.Theheadfield in theadminnode points to the head of that sequence (i.e., containsthe highest pair).Thebranchnode in the admin node indicates the defaultbranch (or revision) for most RCS operations.If empty, the defaultbranch is the highest branch on the trunk.

Alldeltanodes whose numbers consist of2nfields(n≥2)(e.g., 3.1.1.1, 2.1.2.2, etc.)are linked as follows.All nodes whose first2n-1number fields are identical are linked through thenextfield in order of increasing numbers.For each such sequence,thedeltanode whose number is identical to the first2n-2number fields of the deltas on that sequence is called the branchpoint.Thebranchesfield of a node contains a list of thenumbers 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  /                          \     /                           \   /                            \ /

 

IDENTIFICATION

Author: Walter F. Tichy,Purdue University, West Lafayette, IN, 47907.
Manual Page Revision: 5.6; Release Date: 1995/06/05.
Copyright © 1982, 1988, 1989 Walter F. Tichy.
Copyright © 1990, 1991, 1992, 1993, 1994, 1995 Paul Eggert. 

SEE ALSO

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,Software--Practice & Experience15,7 (July 1985), 637-654.


 

Index

NAME
DESCRIPTION
IDENTIFICATION
SEE ALSO

This document was created byman2html,using the manual pages.
 
ICM Bot detect detector