User Tools

Site Tools

Trace:
rcs_sample_session

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
rcs_sample_session [2025/03/05 03:54] – zilogrcs_sample_session [2025/03/05 15:47] (current) – minor re-wording zilog
Line 1: Line 1:
-====== An Annotated RCS Practice Session ======+==== Annotated RCS Practice Session ====
  
 <code diff> <code diff>
Line 13: Line 13:
 ## Create a test file: ## Create a test file:
 ## RCS supports a handful of keyword tags which can be included in source ## RCS supports a handful of keyword tags which can be included in source
-## files likes so: "$Tag$".  These tags will then be expanded whenever RCS+## files like so: "$Tag$".  These tags will then be expanded whenever RCS
 ## acts upon the file. ## acts upon the file.
- 
 ## ##
 ## fubar test file with 'Id' RCS keyword tag: ## fubar test file with 'Id' RCS keyword tag:
 # #
 $ printf '$Id$\nThis is fubar line one.\n' >fubar $ printf '$Id$\nThis is fubar line one.\n' >fubar
 +
  
 ## Initial file check-in: ## Initial file check-in:
Line 39: Line 39:
 done done
  
-## The current state of our working directory.  Note the special delta file +## The current state of our working directory.  Note the special delta 
-## under ../RCS/ which are used to track changes:+## file under ../RCS/ which are used to track the changes:
 # #
 $ ls -FR $ ls -FR
Line 52: Line 52:
 $ ls -l fubar $ ls -l fubar
 -r--r--r--  1 sdfer  users  73 Mar  3 21:18 fubar -r--r--r--  1 sdfer  users  73 Mar  3 21:18 fubar
 +
  
 ## Checking out RCS-managed files for editing: ## Checking out RCS-managed files for editing:
Line 84: Line 85:
 >> . >> .
 done done
 +
  
 ## Verifying RCS keyword Tag expansion: ## Verifying RCS keyword Tag expansion:
 ## It's a small file so we'll use cat(1) to show current content of fubar.  Note ## It's a small file so we'll use cat(1) to show current content of fubar.  Note
-## the expansion of the "$Id$" keyword tag; these are still commonly used by the+## the expansion of the "$Id$" keyword tag; similar tags are commonly used by the
 ## NetBSD project as can be seen at the top of various /etc/* config files: ## NetBSD project as can be seen at the top of various /etc/* config files:
 # #
Line 160: Line 162:
 2a3 2a3
 > This is fubar line two. > This is fubar line two.
 +
  
 ## Similarly, if we do another check out, make some edits and run the ## Similarly, if we do another check out, make some edits and run the
Line 210: Line 213:
 -r--r--r--  1 sdfer  users  97 Mar  3 21:22 fubar -r--r--r--  1 sdfer  users  97 Mar  3 21:22 fubar
  
-## Instead of using cat(1) lets use the ident(1) command to display the +## Just for fun, instead of using cat(1) lets use the ident(1) command 
-## current state of our RCS keyword tag "$Id$":+## to display the current state of our RCS keyword tag "$Id$":
 # #
 $ ident fubar $ ident fubar
Line 226: Line 229:
 done done
  
-## Re-running ident(1) shows our read-only copy matches the latest checked +## Re-running ident(1) shows our read-only copy now matches the latest 
-## revision, now r1.1:+## checked revision which is now r1.1:
 # #
 $ ident fubar $ ident fubar
Line 236: Line 239:
 ## Checking the logs: ## Checking the logs:
 ## The rlog(1) command can show us the change comments for any checked in ## The rlog(1) command can show us the change comments for any checked in
-## revision.  Be default rlog(1) simply shows ALL changes:+## revision using '-r<ver>'.  Be default rlog(1) simply shows ALL changes:
 # #
 $ rlog fubar $ rlog fubar
Line 255: Line 258:
 Initial revision Initial revision
 ============================================================================= =============================================================================
 +
  
 ## Checking lock states with rlog(1): ## Checking lock states with rlog(1):
rcs_sample_session.1741146857.txt.gz · Last modified: 2025/03/05 03:54 by zilog