Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-tgr!tgr!cosell@BBN-LABS-B.ARPA
From: cosell@BBN-LABS-B.ARPA (Bernie Cosell)
Newsgroups: net.unix
Subject: Using named revisions in RCS, redux
Message-ID: <1800@brl-tgr.ARPA>
Date: Mon, 30-Sep-85 11:37:49 EDT
Article-I.D.: brl-tgr.1800
Posted: Mon Sep 30 11:37:49 1985
Date-Received: Wed, 2-Oct-85 01:19:20 EDT
Sender: news@brl-tgr.ARPA
Lines: 27

No sooner had I sent out my note claiming that there was no easy way to tag
`current' revisions with names than I received a note about a scheme that looks
like it will work like a charm (and from another BBN'er, no less -- I should
have checked my back yard before bothering the net!  Thanks Rich!!)

The key insight is that whereas, in fact, the rcs command does not much know
about current revisions, the ci command *does*..  Instead of trying:

    rcs -nNAME *.c

you do:

    co -l *.c
    ci -f "-mAssigning epoch NAME" -nNAME *.c

and it all works.  Sigh.  And just to rub it in, not long after that trick was
pointed out to me, a SECOND workable scheme came in:

If you happen to be able to anticipate what the next 'named' revision is going
to be, which was not the case for me but I can see that it would be a common
circumstance, you just change your shell files that do all the work for you to
include a
      -Nnextepoch
switch on EVERY ci command.  Then as you deposit each revision,
it is given the correct name automatically.

   /Bernie


Brought to you by Super Global Mega Corp .com