Clarence Brown wrote:
[snip]
> 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?
No, you haven't missed anything. CVS will only add log messages to a
group of files, by directory, at it's best resolution (well, all files
being checked in in a directory are grouped - if only one file was
modified in a directory, only one file will get the log message, except
by user request).
It does have the added advantage that it will keep track of files that
have change, so you won't have to (cvs -nq up).
If I were doing this, I would probably have all the *.log files in the
directory concatted into a single file per directory and use that for a
log message, but I am used to CVS's behavior.
Check out the CVS repository if you are curious how this works:
# cvs -d :pserver:[EMAIL PROTECTED]:/home2/cvsroot login
password 'guest'
# cvs -z3 -d :pserver:[EMAIL PROTECTED]:/home2/cvsroot co
ccvs
Derek
--
Derek Price CVS Solutions Architect
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
Re: Graphics
A picture is worth 10k words, but only if the words describe the
picture. Very few arbitrary sets of 10k words can be adequately
replaced with a picture.
