Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Let Coverity Scan check our "maint" and "master" branches once per week.
Currently, Coverity Scan permits up to 8 builds per week for projects
with 100K to 500K lines of code:
https://scan.coverity.com/faq#frequency
|
|
mirror.fcaglp.unlp.edu.ar seems to be dead.
|
|
|
|
Mention that the #monitoring-plugins link points to a web chat
interface.
|
|
We're going to have a bug squashing sprint on November 28, 2014.
|
|
|
|
Define the "$myself" variable.
|
|
The old certificate expired.
|
|
NAGIOS-NOTIFY-MIB traps could be triggered using non-Nagios software.
|
|
|
|
Most users just "update" from our previous releases, they don't
"migrate" from another project.
|
|
We shouldn't attempt to document Nagios/Naemon/Icinga/whatever
configurations on our site.
|
|
Document the migration from the Nagios Plugins to the Monitoring
Plugins.
|
|
|
|
|
|
The release tarball is now called "monitoring-plugins-2.0.tar.gz".
|
|
|
|
We now have coverity/maint and coverity/master branches.
|
|
Make it a little more obvious to users where to unsubscribe from our
mailing lists.
|
|
Gnulib also installs files into the "build-aux" directory.
|
|
As State Retention is actually implemented by now, it's no longer just a
"Proposal".
|
|
The list of default configuration file path names used by the Extra-Opts
feature has changed. And so has the environment variable that can be
used to specify the location.
|
|
Add ftp://mirrors.ustc.edu.cn/monitoring-plugins/ to our list of
mirrors.
|
|
|
|
Email::MIME sometimes prepends an empty line when returning an email as
string :-/
|
|
This shouldn't happen in practice[tm], but if we receive the header
line "Subject: [monitoring-plugins] ", then we won't touch it anymore.
|
|
Save the original emails into a "backup" folder.
|
|
When wrapping a line that begins with a ">", let all resulting lines
begin with a ">". (Properly handle nested blockquotes, too.)
|
|
Don't wrap long lines in a code block.
|
|
|
|
Modify the wording regarding our continuous integration tests to also
mention Coverity Scan.
|
|
Replace HTML code with Markdown syntax.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Now that we edit the GitHub notifications anyway, lets also strip the
[monitoring-plugins] tag. We don't strip the tags of our other
repositories, so that notifications for them do stand out (on the rare
occasion we receive them).
|
|
Use the committer's real name in the "From:" header of commit
notifications. This is a provisional solution. We'd really like to
teach Mailman to also accept the committer's email address.
|
|
Wrap individual lines instead of formatting whole paragraphs, so that
lists such as
* first item
* second item
aren't rewrapped.
|
|
Replace the nagios-plugins.org certificate with the one for
monitoring-plugins.org, and update the README file.
|
|
Reduce the number of formail(1) calls, and make things a bit more
readable.
|
|
Also catch the case where an issue was closed in a commit message, e.g.:
| Closed #123 via c5dc81cd28a9491115b4d13b959b0fc8e2df9a6c.
|
|
Our procmailrc probably isn't immediately obvious.
|
|
Add an X-Original-From to all emails touched by procmail(1). All emails
are forwarded (as long as there's no loop), so that header line might
always be interesting.
|
|
Have GitHub send notifications to plugins+github@, and try to
distinguish actual user comments from mere status change reports. Right
now, both types of notifications are forwarded to the devel@ list, but
in the future, we could choose to omit the status change emails.
While at it, the messages are also modified to make them more suitable
for being forwarded to a mailing list.
|
|
Some browsers aren't happy with embedding HTTP components into an HTTPS
page.
|
|
|