monitoring-plugins/tools, branch release-1.4.15Monitoring Plugins
https://www.monitoring-plugins.org/repositories/monitoring-plugins/atom?h=release-1.4.152010-07-14T13:22:04ZAdded text re: MD5SUM updates in nightlies, but tarballs not2010-07-14T13:22:04ZTon Voonton.voon@opsera.com2010-07-14T13:22:04Zurn:sha1:9bab433981f6c67b40776d1916baae28a0243124git-notify: Be careful with "--no-merge"2010-07-02T13:28:35ZHolger Weissholger@zedat.fu-berlin.de2010-07-02T13:28:35Zurn:sha1:319e308521e0e460fe0b06ee093248628dda819d
The "-X" option (which asks git-notify to not report merge commits) was
implemented by setting the "--no-merge" option on each invocation of
git-rev-list(1). However, we do not only use git-rev-list(1) to get the
list of new commits, but also to check whether the old branch head (or
tag) is a parent of the new branch head (or tag). For this latter
check, the "--no-merge" option should not be set; otherwise, git-notify
would be fooled to believe that the branch has been rewritten if the old
head was a merge commit.
tools/distclean: use git-clean when possible2010-04-28T09:28:22ZThomas Guyot-Sionnestdermoth@aei.ca2010-04-28T09:28:22Zurn:sha1:b48c2bdd59783197c93cde531e6e8b9747c0a88f
git-clean is much faster and more reliable...
Also add confdefs.h in gitignore, although this file is normally removed
at the end of the configure script.
git-notify: Fix the ordering of commits2010-04-14T14:22:21ZHolger Weissholger@zedat.fu-berlin.de2010-04-14T14:22:21Zurn:sha1:ee06edc646129bd1ab7f2c1ffe1fbfdf2e8290bf
If notifications for multiple commits are created, sort them
chronologically instead of in reverse chronological order.
Sync with the latest Gnulib code (177f525)2010-04-13T01:26:35ZThomas Guyot-Sionnestdermoth@aei.ca2010-04-08T01:11:46Zurn:sha1:74da141e618ef99959d509cb2e7be35a348a39db
Signed-off-by: Thomas Guyot-Sionnest <dermoth@aei.ca>
git-notify: Pipe e-mails directly to sendmail(8)2009-12-07T00:58:21ZHolger Weissholger@zedat.fu-berlin.de2009-12-07T00:58:21Zurn:sha1:45e205f4a6cf38ff0f8ade027a7b6a6c7376a00c
Use sendmail(8) instead of mail(1) in order to be able to set the
"Content-Type" header field on systems where the available mail(1)
command doesn't allow for setting it. This makes the "-H" flag (cf.
commit 71350c5a) unnecessary.
Enable CIA's commit notifications2009-12-06T00:23:41ZHolger Weissholger@zedat.fu-berlin.de2009-12-06T00:23:41Zurn:sha1:78fc8f4909750407585990aa10522d9510a69804
We now use CIA's service to send commit notifications to IRC. They are
currently sent to the #Nagios-Devel channel on Freenode. See:
http://cia.vc/stats/project/nagiosplug/
http://cia.vc/account/bots/15699/
Updated link to sfsnapshotgit2009-11-19T21:55:18ZTon Voontonvoon@nagiosplugins.org2009-11-19T21:55:18Zurn:sha1:4b2265d20c8651046b5e8b65000d93bbbbb481f3Fix fetching of remote branches2009-11-11T14:53:35ZThomas Guyot-Sionnestdermoth@aei.ca2009-11-11T14:53:35Zurn:sha1:175b2c8703ef0ecbcd7d8cb7613fa3cb72c81c12Many fixes to snapshot scripts2009-11-11T10:34:22Zdermothdermoth@nagiosplugins.org2009-11-11T10:23:57Zurn:sha1:bb193973a8767547edc8626df6cea7d154812de5
sfsnapshotgit:
- Use fetch/reset instead to pull to avoid merges on forced updates
sfsnapshot-upload:
- Fix link deletion walking the entire home dir
- Allow CLEAN_TIME=0 (no retention)
- Re-add per-branch links when CLEAN_TIME > 0
- Add many comments