Some users would like to get email when someone 
commits a change to CVS.

<p>For email about changes to SVN repositories, see
<a href="http://chess.eecs.berkeley.edu/ptexternal/wiki/Main/Subversion#SettingupSVNEmail">Setting up SVN Email</a>.

<p>To set up CVS mail, the admin of
the workgroup should go to the Admin-&gt;Configure Group page
and click on <code>CVS mail list</code>.
This will send email to the website managers
who will create the mailing list.
<p>
Group admins should read the softdevel CVS 
<a href="http://chess.eecs.berkeley.edu/softdevel/faq/9.html">How do I set it up so that I get email whenever someone commits a change?</a>
question and follow the instructions.

<p>The second step is to edit the
<code>CVSROOT/loginfo</code> file.
<br><b>GSRC:</b> If the CVS repository home directory is
<code>/home/cvs</code>, then you would edit
<code>/home/cvs/CVSROOT/loginfo</code> by
using cvs itself to check it out.
<br><b>Chess:</b> If the CVS repository home directory is
<code>/home/cvs<b>_chess</b></code>, then you would edit
<code>/home/cvs<b>_chess</b>/CVSROOT/loginfo</code>
(For details, see
<a href="http://www.loria.fr/~molli/cvs/doc/cvs_2.html#SEC20"><code>http://www.loria.fr/~molli/cvs/doc/cvs_2.html#SEC20</code></a>
)
<br>For CHESS, E3s, Embedded or Trust CVS repositories,
substitute in the appropriate directory
(<code>cvs_chess</code>, <code>cvs_e3scenter</code>,
<code>cvs_embedded</code>, <code>cvs_trust</code>.
<br/>For CHESS:
<pre>
cvs -d :ext:source.eecs.berkeley.edu:/home/cvs_<b>chess</b> co CVSROOT
</pre>

Then edit <code>CVSROOT/loginfo</code>.
<br><b>GSRC:</b> If the list is on gigascale, add a line like:
<pre>
mvsis/.* mailx -s "%s" mvsis-cvs@gigascale.org
</pre>
<br><b>Chess:</b> If the mailing list is on <code>chess.eecs.berkeley.edu</code>
<pre>
mvsis/.* mailx -s "%s" mvsis-cvs@chess.eecs.berkeley.edu
</pre>

<blockquote>
Note that the <code>%s</code> should be inside double quotes, see the CVS <code>NEWS</code> file for
 changes between cvs-1.11 and cvs-1.11.1 for details.
See also <a href="http://embedded.eecs.berkeley.edu/dopsysadmin/faq/42.html#loginfo">loginfo section of "How do I install CVS?"</a>
</blockquote>

<b>OR</b> See below for using log_accum.pl, which
gives better results.

<br>then commit your changes:
<pre>
cvs commit -m "Added cvs mail for mvsis" loginfo
</pre>
When you do the commit, the 
<code>/home/cvs/CVSROOT/loginfo</code> file will
automagically be updated.

<h2>Chess Setup</h2>

<ol>
<li>Check out a copy of chess CVSROOT:
<pre>
cvs -d :ext:source.eecs.berkeley.edu:/home/cvs co CVSROOT
</pre>
<li>Edit <code>commitinfo</code>
<pre>
^ptII $CVSROOT/CVSROOT/commit_prep.pl
</pre>
<li>Edit <code>loginfo</code>
<pre>
^ptII $CVSROOT/CVSROOT/log_accum.pl %s
</pre>
Note that there is no need to use double quotes around
the <code>%s</code>.

<li>Edit <code>mailhost</code>
<pre>
ptII ptexternal-cvs@chess.eecs.berkeley.edu
</pre>
<li>Add and commit:
<pre>
cvs commit -m "Added diffs support for ptII"
</pre>
</ol>
<h3>Chess initial setup</h3>
On Chess, we are using 
<code>CVSROOT/log_accum.pl</code>, which was originally
obtained from Kepler.
<p>Installation hints can be found at
<a href="http://sial.org/howto/cvs-tips/#s3">Email Notification</a>
I did the following:
<ol>
<li>Obtain <code>log_accum.pl</code> and
<code>commit_prep.pl</code> 
<i>You'll need a kepler cvs account</i>
<pre>
cvs -d :ext:brooks@cvs.ecoinformatics.org:/cvs co CVSROOT
</pre>
<li>Check out a copy of chess CVSROOT:
<pre>
cvs -d :ext:source.eecs.berkeley.edu:/home/cvs co CVSROOT
</pre>
<li>Copy <code>log_accum.pl</code> and
<code>commit_prep.pl</code> in to the chess CVSROOT
<li>Edit <code>checkoutlist</code> and add
<pre>
commit_prep.pl
log_accum.pl
mailhosts
</pre>
<li>Edit <code>log_accum.pl</code>
<br>I changed how the mailhost file is handled so that
it names the entire mailing list name.
<li>Edit <code>commitinfo</code>
<pre>
^ptII $CVSROOT/CVSROOT/commit_prep.pl
</pre>
<li>Edit <code>loginfo</code>
<pre>
^ptII $CVSROOT/CVSROOT/log_accum.pl %s
</pre>
<li>Edit <code>mailhost</code>
<pre>
ptII ptexternal-cvs@chess.eecs.berkeley.edu
</pre>
<li>Add and commit:
<pre>
cvs add commit_prep.pl log_accum.pl mailhosts
cvs commit -m "Added diffs support"
</pre>
</ol>

<h2>Users with restricted accounts</h2>
If a user has a restricted account on the webserver,
then make sure they have access to a <code>mail</code>
program.  If the user does not have access to 
a <code>mail</code> program, then you will see
<pre>
Mailing the commit message...
sh: mail: not found
</pre>
Locally, we did:
<pre>
cp /usr/ucb/mail /users/cvsuser/bin
</pre>
<h2>Users with non-eecs addresses</h2>
If there are cvs users who do not have <code>@eecs.berkeley.edu</code> email addresses, then
further modifications are necessary
<ol>
<li>Create a <code>~/.forward</code> file for the user.
<br>For example, <code>~elvis/.forward</code> would
contain <code>elvis@graceland.com</code>. 
<li>Edit <code>/etc/mail/sendmail.cf</code>
and add the user to the line that starts with
<code>C{E}root</code>.  This will prevent email from
that user being masqueraded to <code><i>user</i>@eecs.berkeley.edu</code>
<li>The loginfo file should have a line like
<pre>
reap/.* /home/cvs_chess/CVSROOT/log.pl -m reap-cvs@chess.eecs.berkeley.edu -s %s
</pre>
</ol>
<p><b>Security note:</b>
At this time, anyone who has cvs write access to
the repository can make the above change.  However, this 
seems a little risky, so we are not telling anyone about it.