Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>We can easily do this using ViewVC (or ViewCVS as it was called formerly). What it does is build a SQL database of all files and their commits (with comments and authors) that you can easily query in many ways.</p> <p>You can download it from <a href="http://www.viewvc.org/" rel="nofollow noreferrer">http://www.viewvc.org/</a>. You will have to set up a MySQL server to store the data and have access to the physical repository directory on the CVS server to import your existing repository commits via the <code>cvsdbadmin</code> tool:</p> <pre><code>cvsdbadmin rebuild /var/lib/cvs </code></pre> <p>where <code>/var/lib/cvs</code> is your repository location. The database connection info is stored in the ViewVC config file.</p> <p>Depending on the repository size this might run anywhere from a few seconds to several hours. Once it is finished, you can use regular SQL query tools to find out all sorts of information about your commits - we use it to very quickly generate change logs. Using a <a href="http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_18.html" rel="nofollow noreferrer" title="CVS loginfo">CVS loginfo script</a> (also included with ViewVC) we update the database on-the-fly whenever someone commits a file to CVS.</p> <p>It can also be very helpful if you committed something by accident (see <a href="http://dschneller.blogspot.com/2007/09/value-of-cvs-commit-database.html" rel="nofollow noreferrer" title="this blog post">this blog post</a>); as CVS commits are not transactional this can be a tough one to figure out.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload