cmd:rcs give a new version 

co -l media.sh
ci -u -m'- bump up version #' -f -r6.0 !$

Ref, if no -f:

$ ci -u -r6.0 media.sh
RCS/media.sh,v  <--  media.sh
file is unchanged; reverting to previous revision 5.39
done

documented on: 2007-11-17

cmd:rcs new version 

*Tags*: milestone,

Usage 

release_tag=
release_tag=new_synopsis_syntax
cat > $ttf.chg.std
> $ttf.chg.more
cat > $ttf.chg.more
cat $ttf.chg.std $ttf.chg.more
ci -u -r5.0 -m"`!!`" *h
rcs -n"$release_tag": !$

Test History 

$ ci -i -u -r2.0 -t-'.' -m'.' 11getlog.lst
11getlog.lst,v  <--  11getlog.lst
initial revision: 2.0
done
$ rcs -nnew_milestone1: !$
RCS file: 11getlog.lst,v
done
$ rlog !$
RCS file: 11getlog.lst,v
Working file: 11getlog.lst
head: 2.0
branch:
locks: strict
access list:
symbolic names:
        new_milestone1: 2.0
keyword substitution: kv
total revisions: 1;     selected revisions: 1
description:
.
----------------------------
revision 2.0
date: 2000/09/01 17:17:48;  author: tong;  state: Exp;
.
=============================================================================
rcs -nnew_milestone1: !$

documented on: 2000.09.01 Fri 14:13:45

fix cmd:rcs file comment 

Synopsis 

How to amend version comment?

Solution Synopsis 

documented on: 2006.11.27

cmd:rcs tagging 

*Tags*: tag rcs

Usage 

date '+%Y%m%d'
date '+%y%m%d'
rcs -n"Rhl9_v1_040117": `rflla`
rcs -n"v3-UDS": argv_show.pl
rcs -n"v2-pass_through":1.5 argv_show.pl
symbolic names:
       v2-pass_through: 1.5
       v3-UDS: 1.6

Explain 

Note a version tag applies to the current rivision that the file is actually at. So, add it before checking in a major change if you want to give a finial point. Otherwise, check in your last minute changes and then mark it as a milestone version tag.

The syntax is

rcs -nTAG: file

Working history 

No dots allowed in version tag 
$ rcs -nRel_1.1.0: spamfree.*
rcs: invalid symbol `Rel_1.1.0'
rcs aborted
$ rcs -nRel_1_1_0: spamfree.*
RCS file: RCS/spamfree.doc,v
done
[...]
rcs -nnew_name_conv_0: ~/bin/.profile_
ci -u -m'new name convention' ~/bin/.profile_
rcs -nnew_name_conv_1: ~/bin/.profile_

In cases of major changes, add tags before & after the change and comment the tag when checking in

Help 

> I'm trying to use rcs to do version control on my own source files
> now. The problem to me is that rcs control the revision for each
> individual file. When some changes require several files be updated
> at the same time, how can I managed that, so that I can easily go
> back?

attach a version tag to the files need to be updated at the same time:

rlog brief-s.el > brl0
rcs -nnametag: brief-s.el
rlog brief-s.el > brl1
rcs -n'release1': brief-s.el
rlog brief-s.el > brl2
$ diff -wc brl0 brl2
*** brl0   Tue Jun 13 13:31:14 2000
--- brl2        Tue Jun 13 13:33:29 2000
***************
*** 7,12 ****
--- 7,14 ----
        tong: 1.2
  access list:
  symbolic names:
+       release1: 1.2
+       nametag: 1.2
  keyword substitution: kv
  total revisions: 2;   selected revisions: 2
  description:

History 

History 
$ rcs -n'release 1.0': brief-s.el
rcs: invalid string 1.0: after option -n or -N
$ rcs -n'release1.0': brief-s.el
rcs: invalid symbol `release1.0'
rcs aborted
History 
$ rcs -n'Finial version for p5903:' *.java
rcs: invalid string version for p5903: after option -n or -N
$ rcs -n'Finial_version_for_p5903:' *.java
RCS file: RCS/Knn.java,v
done

documented on: 2000.06.13 Tue 13:38:00