From: Andrew Hamilton <alphahamilton@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Drop net-analyzer/nagios-* to maintainer-needed
Date: Sat, 25 Jan 2014 12:22:24 -0500 [thread overview]
Message-ID: <52E3F2D0.8030601@gmail.com> (raw)
In-Reply-To: <52E3C916.3010609@gentoo.org>
On 1/25/2014 9:24 AM, Markos Chandras wrote:
> On 11/10/2013 06:12 AM, Johann Schmitz wrote:
>> - gpg control packet
>>>> I already have too many packages to take care of but my company
>>>> is using nagion on Gentoo so I take care of it. Although I
>>>> wouldn't mind if somebody else helps with the packages as well.
>>
>> We use Nagios on many servers at work, so i can help out with these
>> packages too.
>>
>>> ... git overlay for easier nondev contributions? :)
>>
>> A git repo would be useful if there are many changes to the code (e.g.
>> plugins). From what i see in the buglist, most of the bugs are ebuild
>> related (bumps, compile and installation issues).
>>
>>
> (picking a random email from the thread)
>
> ping again. 3 months later, the list of bugs remain the same. Shall we
> consider dropping it to maintainer-needed?
>
I would be happy to proxy-maintain these packages.
Andrew Hamilton
next prev parent reply other threads:[~2014-01-25 17:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 0:14 [gentoo-dev] Drop net-analyzer/nagios-* to maintainer-needed Markos Chandras
2013-11-09 1:17 ` Chris Reffett
2013-11-09 10:16 ` Lars Wendler
2013-11-09 13:13 ` Alex Alexander
2013-11-09 15:20 ` Diego Elio Pettenò
2013-11-09 15:30 ` Alex Alexander
2013-11-09 15:43 ` Diego Elio Pettenò
2013-11-09 15:58 ` Rich Freeman
2013-11-09 23:25 ` Alex Alexander
2013-11-09 17:47 ` Tom Wijsman
2013-11-10 22:27 ` Matthew Thode
2013-11-23 13:15 ` Markos Chandras
2013-11-25 8:00 ` Diego Elio Pettenò
2013-11-10 6:12 ` Johann Schmitz
2014-01-25 14:24 ` Markos Chandras
2014-01-25 17:22 ` Andrew Hamilton [this message]
2014-01-26 1:57 ` Chris Reffett
2014-01-26 10:33 ` Markos Chandras
2014-01-25 18:52 ` 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=52E3F2D0.8030601@gmail.com \
--to=alphahamilton@gmail.com \
--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