throbber
Next: Quick tour, Previous: Credits, Up: Overview [Contents][lndex]
`
`1.2 Concepts
`
`• Interaction model
`
`• Working file
`
`■ RCS file
`
`• Fundamental operations
`
`• Keywords
`
`1.2.1 Interaction model
`
`The interaction model is straightforward. For each working file, you initialize its RCS file
`once, then enter a cycle of checkout, modification, and checkin operations. Along the way,
`you can tweak some of the RCS file's metadata, as well. All of this is done through RCS
`commands; you need not modify the RCS file directly (and in fact you should probably
`avoid doing so lest RCS become confused). This model is somewhat analogous to using a
`library (of books). With a library, you sign up for a library card (initialize), then enter a cycle
`of taking a book home (checkout), enjoying it (NB: without modification, one hopes), and
`returning it to the library (checkin).
`
`Furthermore, you can compare revisions in the RCS file against each other, examine the
`user- (hopefully high) quality descriptions of the changes each revision embodies, merge
`selected revisions, and so forth.
`
`1.2.2 Working file
`
`RCS commands operate on one pair of files at a time. The working file is what you
`normally view and edit (e.g., a file of C programming language source code named a. c).
`Because the working file's contents can be extracted from the RCS file (called instantiating
`a working file), it can be safely deleted to regain some disk space.
`
`1.2.3 RCS file
`
`The RCS file is a separate file, conventionally placed in the subdirectory Res, wherein RCS
`commands organize the initial and subsequent revisions of the working file, associating
`with each revision a unique revision number along with the remembered particulars of the
`checkin that produced it. It also contains a description of the working file and various other
`metadata, described below.
`
`001
`
`GOOGLE 1044
`
`

`

` ÿÿ ÿ
`ÿ
`
ÿ 
ÿ
 ÿ
`ÿ ÿ
 ÿ ÿÿ
ÿ
`ÿ ÿ

`ÿÿ ÿ!!ÿ"#$ !
`%ÿ&'()*)+,ÿ,./0'&ÿ
`ÿ ÿ12  ÿ12ÿ
ÿ1ÿ ÿ
ÿ
ÿ1ÿ ÿ2ÿ ÿ
`0&3,45ÿ,./0'&ÿ
`ÿ ÿ
ÿ12ÿ
ÿ2
`ÿ
`6 2 ÿ1ÿ
!ÿ%ÿ2
`
ÿ12ÿ ÿ

`
`
ÿ6 ÿ ÿ12  ÿ12ÿ
ÿ ÿ

`ÿ
`ÿ
` ÿ
ÿ1ÿ+,ÿ75'ÿ7&.,8!ÿ% ÿ2
`ÿ 2
`6

`!ÿ9
2ÿ: 6 ;
`<#<ÿÿÿÿÿÿÿÿÿ>>ÿ?@ ABACDÿDEFG@?ÿHC?ÿADAIA"Jÿ$K@$LADÿMINOA$"JJNPQ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿG?"D$KÿDEFG@?Rÿ<
`S#T#<#TUÿÿÿÿ>>ÿFC?@ÿ$CFOJA$"I@VÿMO@?K"OBÿ"HI@?ÿFE$KÿWD"?JNÿK"$LADWPQ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿG?"D$KÿDEFG@?RÿS#T#<
`XXX#XXX#XXXÿ>>ÿDCIÿ"ÿ "JAVÿ?@ ABACDÿDEFG@?Q
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿKCY@ @?ÿ"ÿO@?H@$IJNÿ "JAVÿG?"D$KÿDEFG@?
` ÿ0&3,45ÿZ+),7ÿ
ÿ ÿ
2 ÿ12  ÿ
`ÿ ÿ2
`
ÿ12ÿ
2ÿ1ÿ2
ÿ 
`12  [
`ÿ2  ÿ2!ÿ
ÿ
6ÿ ÿ,'\7ÿ5)]5'&ÿ12  ÿ
2ÿ2
`
ÿ12ÿ ÿ
ÿ

` ÿ2  ÿ2!ÿ ÿ  
`12ÿ2
`
ÿ
ÿ ÿ12  ÿ
`ÿ ÿ ÿ7)Zÿ
ÿ 
`12  ÿ
2ÿ0&3,45ÿ7)Z!ÿ
ÿ ÿ: 6 ;
`<#<ÿÿÿÿÿÿÿÿÿ>>ÿCDÿI?EDLQÿDCÿG?"D$KÿOCADIQ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿD@^IÿKAWK@?ÿG?"D$KÿDEFG@?RÿÿÿU
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿD@^IÿKAWK@?ÿ?@ ABACDÿDEFG@?Rÿ<#U
`S#T#<#TUÿÿÿÿ>>ÿDCIÿCDÿI?EDLQÿG?"D$KÿOCADIRÿÿS#T
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿD@^IÿKAWK@?ÿG?"D$KÿDEFG@?RÿÿÿS#T#U
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿD@^IÿKAWK@?ÿ?@ ABACDÿDEFG@?RÿS#T#<#TX
`XXX#XXX#XXXÿ>>ÿDCIÿCDÿI?EDLQÿG?"D$KÿOCADIRÿÿXXX#XXX
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿD@^IÿKAWK@?ÿG?"D$KÿDEFG@?RÿÿÿXXX#XXX#XXT
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿD@^IÿKAWK@?ÿ?@ ABACDÿDEFG@?RÿXXX#XXX#XXX#<
`_ÿ 
ÿ
ÿ 
`ÿ2ÿ
ÿ 
`  ÿ2
`

`ÿ ÿÿ ÿ 6
`ÿ2  ÿ
ÿ ÿ`'a3.b7
`0&3,45ÿ!!ÿ ÿ12  ÿ

`ÿ6ÿ
22
`6

`ÿ
ÿ ÿ

`ÿ2ÿ  cÿ
`ÿ ÿ
`ÿ 
`*d/0+b)4ÿ,3/'*ÿ ÿ 
`ÿ
ÿ
`
`
 

`ÿ1ÿ ÿ
`2
`66 ÿ ÿ62
` 1 
`  ÿ
`1
ÿ ÿ ÿ2 ÿ12  ÿ
2ÿ2
`
ÿ12!
` ÿÿ ÿ
 
`ÿ
ÿ6
`ÿ
ÿ
2 
ÿ
`ÿ
ÿ6 ÿ
`ÿ344'**ÿ4+,7&+b
`Z+b)4d!ÿ ÿ2
`ÿ
`ÿ ÿ 
`ÿ
ÿ
`2 
`!ÿ_ÿ
6ÿ
 ÿ

`ÿ
`2
`ÿ 
`ÿ ÿ
ÿ 
`ÿ ÿ ÿÿ
 
`!ÿ ÿ
`
ÿ
`ÿ ÿ 
`ÿ
ÿb+48*ÿ!!ÿ
`
`
 
ÿ1ÿ
`
`2 ÿ ÿ ÿ2
`
ÿ12!ÿ_ÿ ÿ
 ÿefghijkgRhglimÿ:
`
`ÿ ÿ 
`ÿ
 
`
`002
`
`

`

`username may modify revno (that is, do a checkin operation to deposit the next higher
`revision, or a higher revision numberon the same branch as revno).
`
`1.2.4 Fundamental operations
`
`The checkin operation records the contents of the workingfile in the RCSfile, assigningit
`a new (normally the next higher) revision numberand recording the username, timestamp,
`state (a short symbol), and user-supplied log message(a textual description of the
`changesleadingto that revision). It uses diff to find the differences betweenthetip of the
`default branch andthe workingfile, thereby writing the minimal amountof information
`neededto be able to recreate the contents of the previous tip.
`
`1.2.5 Keywords
`
`The keywords and their values are:
`
`Author
`
`The login nameof the user who checkedin the revision.
`
`Date
`
`The checkoutoperation identifies a specific revision from the RCSfile and either displays
`the content to standard outputor instantiates a workingfile, overwriting any current
`instantiation with the selected revision. In either case, the content may undergo keyword
`expansion, which replacestext of the form ‘$keyword$’ with (possibly) different text
`comprising the keyword andits value, depending on the current keyword expansion mode
`(see Substitution mode option).
`
`  ÿ
`ÿ

`ÿ ÿ ÿ ÿ
ÿ ÿ ÿ   ÿ ÿ
  ÿÿÿ 
`  ÿ ÿ ÿ ÿ  ÿ ÿ ÿÿ ÿ  ÿ ÿ !"
`#$%$&ÿ()*+,-.*/,0ÿ12.3,/41*5
`6ÿ7879:ÿ   ÿ 
ÿÿ ÿ ÿÿ;  ÿ <ÿ ÿÿ=>?ÿ <ÿ   ÿ 
`
` ÿ;ÿ  <<
`ÿÿÿ !ÿ  ÿ ÿ 
ÿ 
ÿÿ ÿ  
` @@ÿ ÿ ÿ
` <!ÿ 
ÿA< 
ÿBCÿ Cÿ ÿ <ÿ
  ÿ ÿ
` ÿ<
ÿ ÿ ÿ  !"ÿEÿÿ+4FFÿ ÿ 
ÿÿ
ÿ ;ÿÿ ÿ ÿ
`
 <ÿ  ÿ 
ÿÿ;  ÿ <ÿ
`ÿ;  ÿÿ   <ÿ  ÿ ÿ    
`

ÿ ÿ ÿ <ÿ ÿ ÿÿ ÿ ÿÿ ÿ "
`6ÿ7879@ÿ   ÿ
  ÿ ÿ  ÿ  ÿ ÿÿ=>?ÿ <ÿ 
ÿ ÿ
<
`
`ÿ ÿ ÿ 

ÿ ÿ ÿ   ÿ ÿ;  ÿ <ÿ ;  ÿ 
`ÿ
`    ÿ; ÿÿ<
ÿ  "ÿEÿ ÿ ÿÿ ÿ
`ÿ
 ÿ9GH I
`JK :ÿ; ÿ< ÿÿ ÿÿ ÿLMNOPQRSTMUÿ; ÿ  <
`!ÿ
ÿ
`   ÿÿ
`; 
ÿ 
ÿ ÿBÿ

ÿ ÿÿÿ
`; 
ÿ  ÿ

`ÿ?   ÿ
ÿ  !"
`#$%$VÿW.XY13+5
`6ÿ
`; 
ÿ 
ÿ ÿ <ÿ Z
`[\]^_`6ÿ<  ÿ ÿ ÿÿÿ; ÿ
ÿ ÿÿ  "
`ab]c6ÿ
ÿ 
ÿ ÿÿ  ÿ; ÿ
ÿ "ÿd
`ÿ <
ÿ ÿ 

ÿ e 
`
` "
`fcbgc`hÿ 

ÿ
ÿ   ÿÿ  <ÿ=>?ÿ < ÿÿ  ÿ ÿ
`
`
ÿ 
ÿ ÿÿ  ÿÿ ÿ 
ÿÿ< ÿ ÿ< 
!"ÿd
`ÿ <
ÿ 
` 

ÿ e ÿ "
`ig? ÿ ÿLjOkTOSUÿÿ ÿ <
`ÿÿ  ÿ  ÿ ÿ
 
`ÿ  !"
`l_mnc`6ÿ<  ÿ ÿ ÿÿÿ; ÿ< 
ÿÿ  ÿ
`ÿ ÿ ÿ< 
!"
`l_o
`
`The date and time the revision was checkedin. Mayinclude an appended timezone
`offset.
`
`Header
`
`A standard headercontaining the absolute RCS filename, the revision number, the
`date and time, the author, the state, and the locker(if locked). May include an
`appendedtimezone offset.
`
`Id
`
`Sameas‘Header’, except that only the basename appears (no directory components).
`
`Locker
`
`The login nameof the user who locked the revision (emptyif not locked).
`
`Log
`
`003
`
`003
`
`

`

`The log message supplied during checkin, preceded by a headercontaining the RCS
`filename, the revision number, the author, and the date and time. May include an
`appendedtimezone offset.
`
`Existing log messagesare not replaced. Instead, the new log message is inserted
`after ‘$Log:...$’. This is useful for accumulating a complete change log in a source
`file.
`
`Eachinserted line is prefixed by the string that prefixes the ‘Logs’ line. For example,
`if the ‘$Log$’ line is
`
`// $log:
`
`tan.cc $
`
`then RCSprefixes eachline of the log with ‘// ’ (slash, slash, space). This is useful
`for languages with commentsthat go to the end oftheline.
`
`The convention for other languagesis to use a ‘ * ’ (Space, asterisk, space) prefix
`inside a multiline comment. For example, theinitial log comment of a C program
`conventionally is of the following form:
`
` ÿÿ ÿ
` 
 ÿ
`
ÿ 
ÿ   ÿÿ ÿ  ÿ

ÿ ÿ
`
 ÿ ÿ

ÿ
`ÿ ÿ
` ÿ  ÿ ÿ ÿ  ÿ
ÿ ÿ

` ÿ 
`   ÿ
ÿ
`

ÿÿ ÿ ÿÿ   ÿ  ÿ ÿ!ÿÿ ÿ
ÿ

`
` ÿ"#$%&'(((#)ÿ
ÿ
ÿ
`
`ÿÿ 
`
` 
ÿ ÿ ÿ ÿÿ
ÿ ÿ
`
`
  ÿ
 ÿ
ÿ
ÿ 
 ÿÿ ÿ
ÿ ÿ 
ÿ ÿ"#$%&#)ÿ
ÿ*ÿ  
`
ÿ ÿ"#$%&#)ÿ
ÿ

`++ÿ#$%&'ÿ-./(00ÿ#
` ÿÿ 
ÿ  ÿ
ÿÿ ÿÿ!
 ÿ"++ÿ)ÿ1  ÿ  ÿ 2ÿ
ÿ
ÿ
`
`
`ÿ 
` ÿ!
 ÿÿ ÿÿÿ ÿ ÿÿ ÿ

` ÿ
ÿÿ ÿ 
` ÿ
ÿÿ
`ÿ ÿ"ÿ3ÿ)ÿ1 ÿ 
ÿ 2ÿ 

`

ÿ ÿ
`

ÿÿ*ÿ  ÿ ÿ


ÿÿÿÿ ÿÿ  
`
 ÿ
ÿÿ ÿ!
ÿ4
`+3ÿ3ÿ#$%&#
`ÿ3+
`*ÿ !  ÿ 


ÿ!
 ÿ ÿ
ÿÿÿ
ÿ ÿÿ 
ÿ
ÿ"+3)ÿÿ"53)
`
`
`  ÿÿ 
 ÿ!
ÿ ÿ
 ÿÿ
ÿ
ÿ ÿ ÿ
 ÿÿ"+)
`ÿ"5)6ÿ !ÿ
ÿ
` ÿ
ÿÿ  ÿ 
` ÿÿÿ
 ÿ
`789: ÿ
ÿ ÿ
` ÿÿ ÿ
`ÿ ÿ

ÿ
ÿ ÿ*ÿ  ÿ"0%ÿ;<=%>)
` ÿ"#?.@>'ÿ=%>ÿ#)ÿA
ÿBCÿ ÿD
`ÿ"#?.@>'ÿ#)
`EFGHIJ: ÿ  ÿÿ ÿÿ

`E:KILIMN ÿ

ÿ
`ÿ 
 ÿÿ ÿ


`GMOPQ: ÿ 
`ÿÿ
 
`GR8R:
`
`For backwards compatibility with older versions of RCS, if the log prefix is ‘/*’ or ‘(*’
`surroundedby optional white space, inserted log lines contain a space instead of‘/’
`or ‘(’; however, this usage is obsolescent and should not be relied on.
`
`/*
`* $Llog$
`*/
`
`Name
`
`The symbolic name used to checkout the revision, if any. For example, ‘co -rJoe’
`generates ‘$name: Joe $’. Plain co generates just ‘$name: $’.
`
`RCSfile
`
`The basename of the RCSfile.
`
`Revision
`
`The revision number assignedto the revision.
`
`Source
`
`The absolute RCSfilename.
`
`State
`
`004
`
`004
`
`

`

`The state assigned to the revision with the -s option of res orci.
`
`
` ÿÿ 
`ÿ ÿ ÿ
  ÿ ÿ ÿÿ  ÿ ÿÿ
ÿ
`ÿ !"ÿ#$%ÿ&$' #(ÿ)$* (%ÿ+,ÿ-'$' .ÿÿÿ/)#00(1/20*1
`
`Next: Quick tour, Previous: Credits, Up: Overview [Contents][Index]
`
`005
`
`005
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket