*Tags*: tag rcs
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.6a 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
$ 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
> 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:$ 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