Re: Standard Versioning for SARE files

[Justin Mason <jm...@jmason.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Guys -- how's about using SVN or similar?  even CVS?  distributed version
control rocks ;)

- --j.

Smart,Dan writes:
> Do *REALLY* need to try RCS. If its installed already, you will be up and
> running in 2 minutes TOPS!
> 
> You start using RCS to maintain versions in three steps.
> 1. Create a subdirectory ./RCS in your work directory.
> 2. Add the following keys to top of the file:
>    ## $Id$
>    ## $Log$
> 3. Check in with `ci -l 99_something_blah
>    the -l makes it automatically checked out to you.
>    
> By default, its status is Experimental (Exp)
> Just add a -sStable (or Stab) to set status to Stable.
> 
> Notes are prompted for when you do a check-in (ci -l -sStable
> 99_something_blah)
> 
> Man ident to see all the variables RCS maintains and increments.
> Note: The $Id$ gives you all the variables.
> 
> Source is located at
> ftp://sunsite.unc.edu/pub/Linux/devel/vc/rcs-5.7.src.tar.gz
> 
> <<Dan>>
> 
> |  "99_something_blah" wherein 99 means that the ruleset is 
> | active  "98_more_blah" wherein 98 means that the ruleset is 
> | stable ... etc. etc. etc. ...
> | 
> | and then the header/comment could state something similar to 
> | the listings at http://www.rulesemporium.com/rules.htm -- 
> | with the Description, Author, License, Status, 
> | LastUpdatedDate, Auto-update, Website and Notes.
> | 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFAnAvwQTcbUG5Y7woRAhuVAKDGO7Wj7rR0lp3GNpVCtddoyG7FWACePd5s
JHUmaAAdWjUCsoLDge1MFT8=
=bczL
-----END PGP SIGNATURE-----