Email address obfuscation in effect -- please
click here to turn it off.
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
Revision Control System: http://www.gnu.org/software/rcs/rcs.html
A fairly default install of RH already has rcs installed. The script I
included is kind of sloppy because it creates an RCS directory in the
same area as the file you are checking in, so you end up with lots of
RCS directories on the system. I had every intention of trying to change
it so that the directory was in one place, and gzip/unzip'd files on the
fly, but I just haven't had the time. I've been told that cvs is a much
better option, but I'm still of the thought that a simple version
control system is better than no version control at all =) The single
biggest advantage I've seen to using it is that it prompts you for a log
entry every time you edit the file.
One caveat about that script. It chmods the "live" files read-only when
they're checked in and out, but I haven't run into a problem with that yet.
It does have some nifty utilities to monitor your changes tho:
rcs (1) - change RCS file attributes
rcsclean (1) - clean up working files
rcsdiff (1) - compare RCS revisions
rcsfile (5) - format of RCS file
rcsintro (1) - introduction to RCS commands
rcsmerge (1) - merge RCS revisions
rlog (1) - print log messages and other information
about RCS files
Rick
Mike Miller wrote:
> On Tue, 5 Nov 2002, Rick Buford wrote:
>
>
> >is plain ol' RCS an option? I have a real simple shell script that makes
> >using it a breeze. Don't remember where I got it, but it'll check the
> >files in and out, creating the RCS directory underneath without much
> >interaction required...
>
>
>
> I'm not familiar with RCS. What does that stand for? Do you know a good
> resource?
>
> Mike
--
To unsubscribe, go to http://mlug.missouri.edu/members/edit.php
Archives are available at http://mlug.missouri.edu/list-archives/