Hi, I think I subscribed at egroups to get this list,
if that's not right please let me know ...
Sorry for the length, but I need to describe where
I'm coming from.
I've been using a DOS port of RCS for a many years
and have developed some Korn Shell scripts to
automate my check in of projects. (using MKS's
ksh for dos).
The main problem I had with RCS besides automating
the checkin to process the whole project, was incorporating
change log messages. I could type them in after the
fact if I could remember all the changes I had made. I might
normally work on changes for several weeks before
checking in a new project version, making many changes
in dozens of files, so remembering changes after the
fact is impossible.
I finally developed a system where I opened a log file
for each source file I was editing in a subdirectory
named log with the same name as the source file. I
use a shell script to check in each source file which
has an existing log file, and the log file is redirected
to the RCS ci command for use as the log message.
I use "$Log:$" comments in the source so RCS adds
the log to the source file. All the individual log files are
also added to a main project log file.
This lets me make notes in the log files as I make
the changes in the source files. However it is a PITA
because I must manually maintain lists that tells my
scripts which files to check in etc.
CVS uses RCS, so the RCS variables I am used to
including in my source will still work right?
What about automatically including log files for the
log messages. Since the commit process automatically
checks in all the changed files, is there anyway to make
it use individual log files for each source file?
>From my reading so far, it looks like CVS provides fewer
logging options than plain RCS. Only a -F and -m which
puts the same log message in each source file. I need an
option like -F which puts a different log file message with
each source file. The other option, entering log messages
after the fact with an editor has the problems of remembering
the changes after the fact.
Since CVS is supposed to be for concurrent development
among many developers, I'm surprised that the change logging
features are no more advanced than plain RCS, or have I
missed something?
Thanks, Cla.
