<feed xmlns='http://www.w3.org/2005/Atom'>
<title>monitoring-plugins/tools, branch archive/state_file</title>
<subtitle>Monitoring Plugins
</subtitle>
<id>https://www.monitoring-plugins.org/repositories/monitoring-plugins/atom?h=archive%2Fstate_file</id>
<link rel='self' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/atom?h=archive%2Fstate_file'/>
<link rel='alternate' type='text/html' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/'/>
<updated>2010-04-28T09:28:22Z</updated>
<entry>
<title>tools/distclean: use git-clean when possible</title>
<updated>2010-04-28T09:28:22Z</updated>
<author>
<name>Thomas Guyot-Sionnest</name>
<email>dermoth@aei.ca</email>
</author>
<published>2010-04-28T09:28:22Z</published>
<link rel='alternate' type='text/html' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/commit/?id=b48c2bdd59783197c93cde531e6e8b9747c0a88f'/>
<id>urn:sha1:b48c2bdd59783197c93cde531e6e8b9747c0a88f</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>git-notify: Fix the ordering of commits</title>
<updated>2010-04-14T14:22:21Z</updated>
<author>
<name>Holger Weiss</name>
<email>holger@zedat.fu-berlin.de</email>
</author>
<published>2010-04-14T14:22:21Z</published>
<link rel='alternate' type='text/html' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/commit/?id=ee06edc646129bd1ab7f2c1ffe1fbfdf2e8290bf'/>
<id>urn:sha1:ee06edc646129bd1ab7f2c1ffe1fbfdf2e8290bf</id>
<content type='text'>
If notifications for multiple commits are created, sort them
chronologically instead of in reverse chronological order.
</content>
</entry>
<entry>
<title>Sync with the latest Gnulib code (177f525)</title>
<updated>2010-04-13T01:26:35Z</updated>
<author>
<name>Thomas Guyot-Sionnest</name>
<email>dermoth@aei.ca</email>
</author>
<published>2010-04-08T01:11:46Z</published>
<link rel='alternate' type='text/html' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/commit/?id=74da141e618ef99959d509cb2e7be35a348a39db'/>
<id>urn:sha1:74da141e618ef99959d509cb2e7be35a348a39db</id>
<content type='text'>
Signed-off-by: Thomas Guyot-Sionnest &lt;dermoth@aei.ca&gt;
</content>
</entry>
<entry>
<title>git-notify: Pipe e-mails directly to sendmail(8)</title>
<updated>2009-12-07T00:58:21Z</updated>
<author>
<name>Holger Weiss</name>
<email>holger@zedat.fu-berlin.de</email>
</author>
<published>2009-12-07T00:58:21Z</published>
<link rel='alternate' type='text/html' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/commit/?id=45e205f4a6cf38ff0f8ade027a7b6a6c7376a00c'/>
<id>urn:sha1:45e205f4a6cf38ff0f8ade027a7b6a6c7376a00c</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Enable CIA's commit notifications</title>
<updated>2009-12-06T00:23:41Z</updated>
<author>
<name>Holger Weiss</name>
<email>holger@zedat.fu-berlin.de</email>
</author>
<published>2009-12-06T00:23:41Z</published>
<link rel='alternate' type='text/html' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/commit/?id=78fc8f4909750407585990aa10522d9510a69804'/>
<id>urn:sha1:78fc8f4909750407585990aa10522d9510a69804</id>
<content type='text'>
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/
</content>
</entry>
<entry>
<title>Updated link to sfsnapshotgit</title>
<updated>2009-11-19T21:55:18Z</updated>
<author>
<name>Ton Voon</name>
<email>tonvoon@nagiosplugins.org</email>
</author>
<published>2009-11-19T21:55:18Z</published>
<link rel='alternate' type='text/html' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/commit/?id=4b2265d20c8651046b5e8b65000d93bbbbb481f3'/>
<id>urn:sha1:4b2265d20c8651046b5e8b65000d93bbbbb481f3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix fetching of remote branches</title>
<updated>2009-11-11T14:53:35Z</updated>
<author>
<name>Thomas Guyot-Sionnest</name>
<email>dermoth@aei.ca</email>
</author>
<published>2009-11-11T14:53:35Z</published>
<link rel='alternate' type='text/html' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/commit/?id=175b2c8703ef0ecbcd7d8cb7613fa3cb72c81c12'/>
<id>urn:sha1:175b2c8703ef0ecbcd7d8cb7613fa3cb72c81c12</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Many fixes to snapshot scripts</title>
<updated>2009-11-11T10:34:22Z</updated>
<author>
<name>dermoth</name>
<email>dermoth@nagiosplugins.org</email>
</author>
<published>2009-11-11T10:23:57Z</published>
<link rel='alternate' type='text/html' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/commit/?id=bb193973a8767547edc8626df6cea7d154812de5'/>
<id>urn:sha1:bb193973a8767547edc8626df6cea7d154812de5</id>
<content type='text'>
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 &gt; 0
	- Add many comments
</content>
</entry>
<entry>
<title>Git commit notifications via post-receive hook</title>
<updated>2009-11-07T09:40:22Z</updated>
<author>
<name>Holger Weiss</name>
<email>holger@zedat.fu-berlin.de</email>
</author>
<published>2009-11-07T09:40:22Z</published>
<link rel='alternate' type='text/html' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/commit/?id=2b442ff177751c5ea17e792c10e6d50d7b922b08'/>
<id>urn:sha1:2b442ff177751c5ea17e792c10e6d50d7b922b08</id>
<content type='text'>
Now that we moved our Git repositories to SourceForge, we don't need to
maintain local clones for generating commit notifications anymore, as
SourceForge provides shell access to the repositories.  Instead, we now
run git-notify as a post-receive hook on the SourceForge server.
Actually, we use a wrapper which executes git-notify with the desired
options and which makes it easy to add other post-receive hooks in the
future.
</content>
</entry>
<entry>
<title>git-notify: Support SourceForge repositories</title>
<updated>2009-11-07T09:40:22Z</updated>
<author>
<name>Holger Weiss</name>
<email>holger@zedat.fu-berlin.de</email>
</author>
<published>2009-11-07T09:40:22Z</published>
<link rel='alternate' type='text/html' href='https://www.monitoring-plugins.org/repositories/monitoring-plugins/commit/?id=c3e2186b15901579cec17aca22646b9dddf2363f'/>
<id>urn:sha1:c3e2186b15901579cec17aca22646b9dddf2363f</id>
<content type='text'>
The Gitweb URLs for repositories hosted by SourceForge are slightly
different than other Gitweb URLs.  The correct URL cannot be specified
via "-u" if we append "/$repos_name.git/?" to that URL as we usually do.
If the new "-S" flag is specified or "notify.sourceforge" is set, we'll
append "/$repos_name;" instead, which makes the "-u" option usable for
SourceForge repositories.
</content>
</entry>
</feed>
