| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
8. History browsing
Once you have used CVS to store a version control history--what files have changed when, how, and by whom, there are a variety of mechanisms for looking through the history.
| 8.1 Log messages | ||
| 8.2 The history database | ||
| 8.3 User-defined logging | ||
| 8.4 Annotate command | What revision modified each line of a file? |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
8.1 Log messages
Whenever you commit a file you specify a log message.
To look through the log messages which have been
specified for every revision which has been committed,
use the cvs log command (see section log--Print out log information for files).
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
8.2 The history database
You can use the history file (see section The history file) to
log various CVS actions. To retrieve the
information from the history file, use the cvs
history command (see section history--Show status of files and users).
Note: you can control what is logged to this file by using the `LogHistory' keyword in the `CVSROOT/config' file (see section The CVSROOT/config configuration file).
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
8.3 User-defined logging
You can customize CVS to log various kinds of
actions, in whatever manner you choose. These
mechanisms operate by executing a script at various
times. The script might append a message to a file
listing the information and the programmer who created
it, or send mail to a group of developers, or, perhaps,
post a message to a particular newsgroup. To log
commits, use the `loginfo' file (see section Loginfo).
To log tags, use the `taginfo' file (see section Taginfo).
To log commits, checkouts, exports, and tags,
respectively, you can also use the `-i',
`-o', `-e', and `-t' options in the
modules file. For a more flexible way of giving
notifications to various users, which requires less in
the way of keeping centralized scripts up to date, use
the cvs watch add command (see section Telling CVS to notify you); this command is useful even if you are not
using cvs watch on.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
8.4 Annotate command
- Command: cvs annotate [
-FflR] [-r rev|-D date] files … For each file in files, print the head revision of the trunk, together with information on the last modification for each line. For example:
$ cvs annotate ssfile Annotations for ssfile *************** 1.1 (mary 27-Mar-96): ssfile line 1 1.2 (joe 28-Mar-96): ssfile line 2
The file `ssfile' currently contains two lines. The
ssfile line 1line was checked in bymaryon March 27. Then, on March 28,joeadded a linessfile line 2, without modifying thessfile line 1line. This report doesn't tell you anything about lines which have been deleted or replaced; you need to usecvs difffor that (see section diff--Show differences between revisions).
The options to cvs annotate are listed in
Quick reference to CVS commands, and can be used to select the files
and revisions to annotate. The options are described
in more detail there and in Common command options.
| [ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by Derek R. Price on April, 13 2004 using texi2html 1.71.
![[ Valid XHTML 1.0! ]](/branding/w3c-valid-xhtml10-44x16.png)
![[ Valid CSS! ]](/branding/w3c-valid-css-44x16.png)
