public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nagios/
Date: Sun, 11 Dec 2016 17:11:31 +0000 (UTC)	[thread overview]
Message-ID: <1481474863.6c1d39fe9d9b02421922d936ecdcf31a657b5977.mjo@gentoo> (raw)

commit:     6c1d39fe9d9b02421922d936ecdcf31a657b5977
Author:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 11 16:47:43 2016 +0000
Commit:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Sun Dec 11 16:47:43 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6c1d39fe

net-analyzer/nagios: remove proxy maintainers from the metadata.

We haven't heard from this package's proxy maintainer in a while, but
new bugs are still being assigned to him. As long as I'm the de-facto
maintainer, I would prefer that they be assigned to me. This commit
removes both the proxied and proxy maintainers, as well as the
proxy-maint project (who gave the OK for this removal).

Package-Manager: portage-2.3.0

 net-analyzer/nagios/metadata.xml | 45 ++++++++++++++--------------------------
 1 file changed, 15 insertions(+), 30 deletions(-)

diff --git a/net-analyzer/nagios/metadata.xml b/net-analyzer/nagios/metadata.xml
index 55c38bf..6d334d5 100644
--- a/net-analyzer/nagios/metadata.xml
+++ b/net-analyzer/nagios/metadata.xml
@@ -2,39 +2,24 @@
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
   <maintainer type="person">
-      <email>andrew@ahamilto.net</email>
-      <name>Andrew Hamilton</name>
-      <description>Maintainer. Assign bugs to him.</description>
-  </maintainer>
-  <maintainer type="person">
-      <email>creffett@gentoo.org</email>
-      <name>Chris Reffett</name>
-      <description>Proxy maintainer. CC him on bugs.</description>
-  </maintainer>
-  <maintainer type="person">
-      <email>mjo@gentoo.org</email>
-      <name>Michael Orlitzky</name>
-  </maintainer>
-  <maintainer type="project">
-      <email>proxy-maint@gentoo.org</email>
-      <name>Proxy Maintainers</name>
+    <email>mjo@gentoo.org</email>
+    <name>Michael Orlitzky</name>
   </maintainer>
   <maintainer type="project">
-      <email>sysadmin@gentoo.org</email>
-      <name>Gentoo Sysadmin Project</name>
+    <email>sysadmin@gentoo.org</email>
+    <name>Gentoo Sysadmin Project</name>
   </maintainer>
   <longdescription>
-    Nagios is a host and service monitor designed to inform you
-    of network problems before your clients, end-users or
-    managers do. It has been designed to run under the Linux
-    operating system, but works fine under most *NIX variants as
-    well. The monitoring daemon runs intermittent checks on
-    hosts and services you specify using external "plugins"
-    which return status information to Nagios. When problems are
-    encountered, the daemon can send notifications out to
-    administrative contacts in a variety of different ways
-    (email, instant message, SMS, etc.). Current status
-    information, historical logs, and reports can all be
-    accessed via a web browser.
+    Nagios is a host and service monitor designed to inform you of
+    network problems before your clients, end-users or managers do. It
+    has been designed to run under the Linux operating system, but
+    works fine under most *NIX variants as well. The monitoring daemon
+    runs intermittent checks on hosts and services you specify using
+    external "plugins" which return status information to Nagios. When
+    problems are encountered, the daemon can send notifications out to
+    administrative contacts in a variety of different ways (email,
+    instant message, SMS, etc.). Current status information,
+    historical logs, and reports can all be accessed via a web
+    browser.
   </longdescription>
 </pkgmetadata>


             reply	other threads:[~2016-12-11 17:11 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-11 17:11 Michael Orlitzky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-03  1:20 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nagios/ Michael Orlitzky
2024-02-18 22:49 Michael Orlitzky
2024-02-18 22:42 Sam James
2024-02-18 19:57 Arthur Zamarin
2024-02-18 19:57 Arthur Zamarin
2024-02-18 19:57 Arthur Zamarin
2023-09-09 23:44 Michael Orlitzky
2023-06-19 21:54 Michael Orlitzky
2023-06-10 11:43 Michael Orlitzky
2023-06-10 11:43 Michael Orlitzky
2023-03-07  2:33 Michael Orlitzky
2023-03-07  2:33 Michael Orlitzky
2022-12-07 18:23 Michael Orlitzky
2022-11-06 11:53 Michael Orlitzky
2022-08-30  1:05 Michael Orlitzky
2022-08-29 12:38 Jakov Smolić
2022-08-12 14:27 Sam James
2022-08-03 17:51 Arthur Zamarin
2022-08-03 16:12 Arthur Zamarin
2022-06-02 17:23 Michael Orlitzky
2020-06-11 12:34 Michael Orlitzky
2020-06-11  8:34 Agostino Sarubbo
2020-06-11  8:31 Agostino Sarubbo
2020-06-11  8:29 Agostino Sarubbo
2020-06-11  8:25 Agostino Sarubbo
2020-06-10 13:01 Agostino Sarubbo
2020-05-10 11:26 Michael Orlitzky
2020-04-17 16:24 Sergei Trofimovich
2020-04-13  9:57 Agostino Sarubbo
2020-04-04 14:11 Michael Orlitzky
2020-04-04 14:11 Michael Orlitzky
2020-04-04 13:27 Agostino Sarubbo
2020-04-03 16:14 Agostino Sarubbo
2020-04-03 16:14 Agostino Sarubbo
2020-04-03 16:13 Agostino Sarubbo
2019-08-31 21:35 Michael Orlitzky
2019-08-31 21:35 Michael Orlitzky
2019-08-15  0:05 Michael Orlitzky
2019-03-02  4:38 Michael Orlitzky
2019-01-19  0:00 Michael Orlitzky
2018-12-02 16:02 Michael Orlitzky
2018-12-02 16:02 Michael Orlitzky
2018-11-28 22:35 Sergei Trofimovich
2018-11-28 22:33 Sergei Trofimovich
2018-11-27 21:55 Thomas Deutschmann
2018-11-27 16:01 Tobias Klausmann
2018-11-26 19:52 Sergei Trofimovich
2018-11-26 15:28 Agostino Sarubbo
2018-09-03 14:21 Michael Orlitzky
2018-08-08 21:08 Michael Orlitzky
2018-06-23 11:40 Michael Orlitzky
2018-06-19 11:46 Michael Orlitzky
2018-06-11 16:28 Aaron Bauman
2017-10-18  1:21 Aaron Bauman
2017-10-13  9:50 Sergei Trofimovich
2017-10-03  0:42 Thomas Deutschmann
2017-09-24 19:50 Sergei Trofimovich
2017-09-24 11:00 Sergei Trofimovich
2017-09-07 20:59 Sergei Trofimovich
2017-08-31 15:18 Matt Turner
2017-08-30 23:53 Michael Orlitzky
2017-08-16 11:57 Michael Orlitzky
2017-06-07 12:40 Michael Orlitzky
2017-03-08 12:50 Michael Orlitzky
2017-03-08  5:16 Jeroen Roovers
2017-03-04 14:02 Agostino Sarubbo
2017-03-02 10:47 Agostino Sarubbo
2017-03-02 10:30 Agostino Sarubbo
2017-02-28 11:22 Tobias Klausmann
2017-02-27 21:49 Michael Weber
2017-02-25 19:29 Michael Orlitzky
2017-01-14 21:05 Michael Orlitzky
2017-01-14 12:01 Jeroen Roovers
2016-12-22  9:34 Agostino Sarubbo
2016-12-20  9:44 Agostino Sarubbo
2016-12-19 14:35 Agostino Sarubbo
2016-12-13 11:30 Agostino Sarubbo
2016-12-13 11:05 Agostino Sarubbo
2016-12-12 15:55 Tobias Klausmann
2016-12-11 17:11 Michael Orlitzky
2016-12-06 11:53 Agostino Sarubbo
2016-12-06 11:50 Agostino Sarubbo
2016-12-05 15:49 Tobias Klausmann
2016-10-28 15:16 Michael Orlitzky
2016-10-28 15:16 Michael Orlitzky
2016-09-26 13:25 Michael Orlitzky
2016-09-21 18:58 Tobias Klausmann
2015-08-31 14:13 Michael Orlitzky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1481474863.6c1d39fe9d9b02421922d936ecdcf31a657b5977.mjo@gentoo \
    --to=mjo@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox