Sending commit messages via mail must be configured by a Codehaus administrator. Administrators should initially configure this on behalf of project committers. The following procedure should be done on beaver.codehaus.org.
cd into the repository's hooks directory. For example:
cd /home/projects/FOO/scm/hooks |
post-commit file and make it executable (sudo chmod 755 post-commit). The contents of the file should include the following (Note: you must change "FOO" to the name of the new repository):
#!/bin/sh
REPOS="$1"
REV="$2"
PATH=/usr/bin:/bin:/usr/local/subversion/bin
PROJECT=FOO
JIRA_URL=http://jira.codehaus.org/secure/ViewIssue.jspa?key=%s
FISHEYE_URL=http://fisheye.codehaus.org/changelog/FOO/?cs=%s
# Note that --from is optional and if omitted the from address will be $COMMITTER@codehaus.org
# JIRA and Fisheye are also optional
svnnotify --repos-path "$REPOS" \
--revision "$REV" \
--svnlook /usr/local/subversion/bin/svnlook \
--to scm@$PROJECT.codehaus.org \
--from scm@$PROJECT.codehaus.org \
--with-diff --subject-cx --handler HTML::ColorDiff \
--jira-url $JIRA_URL \
--viewcvs-url $FISHEYE_URL
|
#!/bin/sh REPOS="$1" REV="$2" PATH=/usr/local/subversion/share/tools/hook-scripts commit-email.pl -s "[FOO]" "$REPOS" "$REV" scm@FOO.codehaus.org |
sudo chgrp groupname post-commit sudo chmod g+w post-commit |
This is not recommended, since it leads to dissemination via the list of messages returned from bad auto-responders and MTAs. Also, it may lead to public replies to the list where personal replies were intended. In addition, the original ``Reply-To:'' header is lost.
If you do want to add a reply-to list header, put
reply-to |
into /home/projects/FOO/scm/headerremove, and
Reply-To: list@host.dom |
into /home/projects/FOO/scm/headeradd.