where the fields (and meanings) are:
O status (O=checked out, F=returned, M=modified, etc... see 'man cvs')
02/04 date of last activity
09:20 time of last activity
STONE user who performed this activity
TAS3/* location within the repository
=TPC= module name (TPC)
~/TAS3/* user's working directory
Some handy options are:
-a return information for ALL users
-e return ENTIRE history (all past activity)
-m (mod) return information for MODULE 'mod'
CVS does not MERELY store the times changes were made, but it also
stores a verbal record of the nature of these changes.
Each time a change is COMMITed to the repository, the user is
prompted to enter a few lines about the nature of his/her changes.
To receive a listing of these LOG entries for any file (or module)
in the repository, issue the command:
cvs log [filename]
If no filename is given, CVS will report all LOG entries
for all modules and/or files in the current directory. This can get long!
A sample log (for the file: bin.make) *might* look like this:
RCS file: /home/sseos/us1/e895/CVS_TAS3/TAS3/bin/bin.make,v
Working file: bin.make
comment leader: "# "
keyword substitution: kv
total revisions: 3; selected revisions: 3
date: 1997/01/30 17:39:00; author: stone; state: Exp; lines: +0 -9
modified makefile to allow parallel linking structure
date: 1997/01/29 21:39:51; author: stone; state: Exp; lines: +1 -1
modified the names of the include files
date: 1997/01/29 19:00:55; author: stone; state: Exp;
Modified makefile structure to accomodate CVS repository
This reports that the current version number (head) is 1.3 .
There are three revisions on record (for versions 1.1, 1.2, and 1.3), and
the associated comments are clearly seen.
The date, time, and author name is automatically added by CVS, so that
when entering comments, all YOU need to do is say what you were doing.
If you only wanted to know the STATUS of the file
(version number, whether it is different from the repository), then you
could have issued the CVS STATUS command:
cvs status [filename]
This command (like LOG), if no filename is given,
will return a report for all modules and/or files in the current
directory. This can also get long!
One such report *might* look like this:
File: bin.make Status: Locally Modified
Version: 1.6 Mon Feb 3 14:38:05 1997
RCS Version: 1.6 /home/sseos/us1/e895/CVS_TAS3/TAS3/bin/bin.make,v
Sticky Tag: (none)
Sticky Date: (none)
Sticky Options: (none)
The status Locally Modified implies that the user has made
changes to this file which he/she has not yet COMMITed. When
the file is in sync with the Repository, its status will be