.\"
.\"     aegis - project change supervisor
.\"     Copyright (C) 1999, 2002, 2005-2008, 2010, 2012 Peter Miller
.\"
.\"     This program is free software; you can redistribute it and/or modify
.\"     it under the terms of the GNU General Public License as published by
.\"     the Free Software Foundation; either version 3 of the License, or
.\"     (at your option) any later version.
.\"
.\"     This program is distributed in the hope that it will be useful,
.\"     but WITHOUT ANY WARRANTY; without even the implied warranty of
.\"     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
.\"     GNU General Public License for more details.
.\"
.\"     You should have received a copy of the GNU General Public License
.\"     along with this program. If not, see
.\"     <http://www.gnu.org/licenses/>.
.\"     Operation
.\"
.nh 2 "Automatic Operation"
.LP
This section describes how to use \fIaedist\fP to automatically send
change sets via e\[hy]mail.
.nh 3 "Sending"
.LP
Change sets can be sent automatically when a change passes integration.
You do this by setting the \fIintegrate_\%pass_\%notify_\%command\fP
field of the project attributes.
.LP
In this example, the \[lq]example\[rq] project sends all integrations to all
the addresses on the \f(CWexample\[hy]developers\fP mailing list.  (The
mailing list is maintained outside of Aegis, \fIe.g.\fP by Majordomo.)
The relevant attribute (edited by using the \fIaepa\fP(1) command)
looks like this:
.E(
integrate_pass_notify_command =
  "aedist \-p $project \-c $change | \e
  mail example\-users";
.E)
.LP
Please note that project attributes are inherited by branches when they
are created.  If you don't want all branches to broadcast all changes,
you need to remember to clear this project attribute \fIfrom the branch\fP
once the branch has been created.  Alternatively, use the \f(CW$version\fP
substitution to decide who to send the change to.
.nh 3 "Receiving"
.LP
\fIwrite this section\fP
.LP
You need to set up an e\[hy]mail alias, with a wrapper around it \- you
probably \fIdon't\fP want "daemon" as a registered developer.
.LP
While \fIaedist\fP(1) makes every attempt to spot potential trojan attacks,
you really, \fIreally\fP want PGP validation (or similar industrial
strength digital signatures) before you accept this kind of input.
.\" vim: set ts=8 sw=4 et :