1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
|
<html>
<head>
<title>Using Triggers</title>
</head>
<body>
<a name="Using_Triggers"></a>
<a href="http://www.regexps.com">The Hackerlab at <code>regexps.com</code></a>
<h2 align=center>Using Triggers</h2>
<small>
<b>up: </b><a href="arch.html#arch">arch</a></br>
<b>next: </b><a href="automatic-triggers.html#Automatic_Triggers">Automatic Triggers</a></br>
<b>prev: </b><a href="triggers.html#arch_Triggers">arch Triggers</a></br>
</small>
<br>
<p>This chapter describes two ways to use triggers: for sending email
about changes to an archive, and for keeping a revision library up to
date (see <a href="revision-lib.html#Revision_Tree_Libraries">Revision Tree Libraries</a>).
</p>
<a name="Sending_Email_Notices_About_Repository_Changes"></a>
<h3 align=center>Sending Email Notices About Repository Changes</h3>
<p><a name="index-pt:0"></a>
<a name="index-pt:1"></a>
<a name="index-pt:2"></a>
<a name="index-pt:3"></a>
<a name="index-pt:4"></a>
<a name="index-pt:5"></a>
</p><p><code>arch</code>
provides four commands designed for use as triggers that send
email about changes to a repository. (See <a href="triggers.html#arch_Triggers">arch Triggers</a>.)
These are:
</p><pre>
larch mail-new-categories
larch mail-new-branches
larch mail-new-versions
larch mail-new-revisions
</pre>
<p>You can create a triggers for sending email with a <code>notify</code>
<code>=rules.archives</code>
configuration rule such as this (here split over
multiple lines to fit the printed page -- in practice, this rule would
be on one line):
</p><pre>
joe.hacker--2002@gnu.org
mail-new-categories:joe@gnu.org
mail-new-branches:joe@gnu.org
mail-new-versions:joe@gnu.org
mail-new-revisions:joe@gnu.org
</pre>
<a name="Updating_a_Revision_Library"></a>
<h3 align=center>Updating a Revision Library</h3>
<p><a name="index-pt:6"></a>
</p><p>You can use triggers to keep a revision library automatically
up-to-date with a rule like this:
</p><pre>
joe.hacker--2002@gnu.org
noop:
noop:
noop:
library-add:--ignore-extra-args
</pre>
<small><i>arch: The arch Revision Control System
</i></small><br>
<a href="http://www.regexps.com">The Hackerlab at <code>regexps.com</code></a>
</body>
|
