RCS and SCCS

[Mike Khaw]

>From article <3493 at rpp386.UUCP>, by jfh at rpp386.UUCP (John F. Haugh II):
> i hate to ask this question[.,;?:!] (there, that gives most of the
> punctuation characters on the keyboard ;-) but i really wanted to
> see an actual (visible ASCII-fied if needbe) RCS file.
> 
> if someone local to dfw would mail me a uuencoded RCS file, i'd
> greatly appreciate it.

There's no need to "ASCII-fy" or uuencode unless the file being RCS'ed
itself contains nonprintable characters.  Here's an actual RCS file
of my .logout file (a toy example, however):

--- RCS/.logout,v ---
head     1.2;
access   ;
symbols  ;
locks    ; strict;
comment  @@;


1.2
date     88.07.02.12.45.09;  author mkhaw;  state Exp;
branches ;
next     1.1;

1.1
date     88.07.02.12.43.31;  author mkhaw;  state Exp;
branches ;
next     ;


desc
@example RCS file
@


1.2
log
@can't embed Log in shell script (no syntax for multiline comments)
@
text
@
# $Header: .logout,v 1.1 88/07/02 12:43:31 mkhaw Exp $

# replaced "Log" header with this comment

clear
@


1.1
log
@Initial revision
@
text
@d2 1
a2 1
# $Header$
d4 1
a4 1
# $Log$
@
--- END of RCS/.logout,v ---

The initial version of the file was:

--- .logout ---
# $Header$

# $Log$

clear
--- END of .logout ---

After checking in the initial version ("ci"), I changed the second comment
line to:

# replaced "Log" header with this comment

and checked the file back in.  You can see that the RCS file starts with
a bunch of administrivial lines, then the complete verbatim latest version,
then diff-like lines for the reverse-delta to the previous version(s).

Mike Khaw
-- 
internet: mkhaw at teknowledge.arpa
uucp:	  {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge.arpa
hardcopy: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303