diff options
author | Holger Weiss <holger@zedat.fu-berlin.de> | 2013-10-28 22:58:36 (GMT) |
---|---|---|
committer | Holger Weiss <holger@zedat.fu-berlin.de> | 2013-10-28 22:58:36 (GMT) |
commit | 3c90a370ea5860ed66d35285aba8304ed4f5c9ba (patch) | |
tree | f1c8e36b2aa17ed6b1b82257fc6d9a8eb39be267 /SUPPORT | |
parent | 739b272b65ab060b5d0f20cc3d89e6c5bc17e32b (diff) | |
download | monitoring-plugins-3c90a370ea5860ed66d35285aba8304ed4f5c9ba.tar.gz |
Update URLs and mailing list addresses
Now that we moved our infrastructure away from SourceForge, update the
URLs and mailing list addresses accordingly.
Diffstat (limited to 'SUPPORT')
-rw-r--r-- | SUPPORT | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -7,8 +7,8 @@ http://www.nagios.org/ to track the current status of commercial | |||
7 | support offerings. | 7 | support offerings. |
8 | 8 | ||
9 | There are two mailing lists associated with Nagios Plugin development: | 9 | There are two mailing lists associated with Nagios Plugin development: |
10 | 'help' (mailto:nagiosplug-help@lists.sourceforge.net), and 'devel' | 10 | 'help' (mailto:help@nagios-plugins.org), and 'devel' |
11 | (mailto:nagiosplug-devel@lists.sourceforge.net). Unless you are fairly | 11 | (mailto:devel@nagios-plugins.org). Unless you are fairly |
12 | certain you have found a bug or that you are requesting a new feature, | 12 | certain you have found a bug or that you are requesting a new feature, |
13 | please direct support requests to 'help'. | 13 | please direct support requests to 'help'. |
14 | 14 | ||
@@ -48,8 +48,8 @@ REPORTING BUGS AND SUBMITTING PATCHES | |||
48 | 48 | ||
49 | Bug reports, investigations of possible bugs, feature requests, and | 49 | Bug reports, investigations of possible bugs, feature requests, and |
50 | patch submissions should be submitted to the development list at | 50 | patch submissions should be submitted to the development list at |
51 | mailto:nagiosplug-devel@lists.sourceforge.net. Please raise an issue first | 51 | mailto:devel@nagios-plugins.org. Please raise an issue first in |
52 | in GitHub, otherwise your email is likely to be missed over time. | 52 | GitHub, otherwise your email is likely to be missed over time. |
53 | 53 | ||
54 | You should identify the version, preferably in the subject line. | 54 | You should identify the version, preferably in the subject line. |
55 | However, to best use developer resources, it is suggested that you | 55 | However, to best use developer resources, it is suggested that you |