-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathCHANGES
166 lines (108 loc) · 5.67 KB
/
CHANGES
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
152
153
154
155
156
157
158
159
160
161
162
163
164
165
0.3-15 | 2011-08-12 09:07:27 -0700
* Updating CHANGES. (Robin Sommer)
0.3-13 | 2011-08-11 10:15:56 -0700
* Mails are now sent out in chronological order. (Robin Sommer)
0.3-12 | 2011-07-31 21:45:00 -0700
* A number of bug fixes. (Robin Sommer)
0.3-7 | 2011-07-30 10:33:30 -0700
* New option --replyto to set a Reply-To header for mails. (Robin
Sommer)
0.3-6 | 2011-07-24 15:52:44 -0700
* Using diff-tree instead of diff as it allows us to give just a
single revision. (Robin Sommer)
* With --allchanges, a revision previously reported in a branch and
now for one of the --allchanges heads, will have only the latter
in the mail subject. (Robin Sommer)
0.3-5 | 2011-07-22 15:59:12 -0700
* Further tweaking allchanges. We now don't do real diffs anymore at
all, that's just not reliable. Instead, we simply always report
new revisions for allchanges heads no matter if they have already
been reported.
0.3-4 | 2011-07-19 19:19:46 -0700
* Fixing the 0.3-3 change for diffs, which didn't work right. (Robin
Sommer)
0.3-3 | 2011-07-17 22:15:14 -0700
* For heads that get full diffs, we now record which diffs we have
already mailed out. This avoid duplicates when stuff is merged into
something else later. (Robin Sommer)
0.3-2 | 2011-07-14 11:17:44 -0700
* Removing debugging output. (Robin Sommer)
0.3-1 | 2011-07-12 14:35:53 -0700
* Fixing a problem with diffing potentially skipping revisions when
facing merges. (Robin Sommer)
0.3 | 2011-05-08 21:33:08 -0700
* Significant speed improvement: we now query git for the branches
reachable from a revision rather than trying to figure it out
ourselves. Based on a suggestion by Simon Marlow.
* Adding git repository to README.
* Compatibility fix to support older git versions. (Simon Marlow)
* New option 'link' to define a URL that will be inserted into
notification mails.
* New option 'repouri' to overide the automatically derived
repository location.
* All options can now indeed be given via git-config (as the README
already claims), and they are now all located in the hooks.*
namespace.
* Integer options are now correctly converted to ints when read from
git-config.
* Internal rewrite of how options are implemented.
* Removing the update-changes script from the repository.
* Now using gitolite's GL_ADMINDIR environment variable to locate
the default sender.cfg.
* We now keep the previous state file as *.bak.
* Fixing a bug with revisions not being part of any head.
* Now hooks.allchanges can be specified via "git config".
* New options, two of them primarily for debugging and manual
generation of notifications.
``--allchanges <branches>``
Lists branches for which *all* changes made to them should
be mailed out as straight diffs to their previous state,
independent of whether the corresponding commit has already
been reported in the past. This might for example make sense
for ``master`` if one wants to closely track any
modification applied. ``<branches>`` is a list of
command-separated names of heads to treat this way.
``--diff [rev1..]rev2``
Mails out diffs between all revisions on the first parent's
way from ``rev1`` to ``rev2``. This option produces output
similar to that of a head moving forward which is listed
with ``--allchanges``. If ``rev1`` is skipped, ``rev2~1`` is
assumed.
This option is primarily for debugging and retropective
(re-)generation of this outut, and does not change the
current notifier state in any way. The main difference to
``--manual`` is that it considers only revision on the first
parent's path, and mails out actual diffs between these.
``--manual [rev1..]rev2``
Mails out notifications for all revisions on the way from
``rev1`` to ``rev2``. If ``rev1`` is skipped, ``rev2~1`` is
assumed.
This option is primarily for debugging and retropective
(re-)generation of this output, and does not change the
current notifier state in any way.
0.2 | 2011-01-07 10:06:31 -0800
* The script now waits a little bit after sending out each mail.
Before, mails sent back-to-back could arrive with identical
timestamps, making it harder to determine their actual order.
0.1-5 | 2011-01-02 10:18:10 -0800
* Updating update-changes.
0.1-4 | 2011-01-01 22:23:53 -0800 | e201aebe6ab827e2b8b33fb302b9d05bde0d9355
* Now mails are also sent when a head updates to now include further
commits that have already been reported earlier (e.g., on
fast-forwards). These mails summarize all revisions on the path from
its previous state to the new head position. This is experimental at
this point.
* The script now checks for "-h" or "--help" as a command-line
option, and prints a short (and not very helpful) usage message
if found.
0.1-3 | 2011-01-01 21:44:11 -0800 | 94154e05ff29522e256803d2cfe9b7d98d28b138
* Renaming the "recipients" options to "mailinglist", as it was
already documented. (Matthias Vallentin)
0.1-2 | 2011-01-01 21:41:09 -0800 | b650d20a8d10c9bc8de20c3715c9b1dab9100288
* Adding "[nomail]" option: if that tag is included in a commit
message, no mail will be send for that change. Also, documenting the
already existing "[nodiff]" option: if included in a commit message,
no diff will be included for that change.
* Adding update-changes script.
0.1 | 2010-12-19 20:30:38 -0800 | 2606f82b91b0984c9de050c001729ce45dfb69cd
* Initial version.