From: Tom Wijsman <TomWij@gentoo.org>
To: wired@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Drop net-analyzer/nagios-* to maintainer-needed
Date: Sat, 9 Nov 2013 18:47:25 +0100 [thread overview]
Message-ID: <20131109184725.0b61ac06@TOMWIJ-GENTOO> (raw)
In-Reply-To: <CAMUzOahY8_cJZbEom79-iFkyf3m-gWA+4m0RU2+NC7FkMO=UUg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
On Sat, 9 Nov 2013 17:30:43 +0200
Alex Alexander <wired@gentoo.org> wrote:
> Herds are definitely not the solution for everything, but they make
> sense when you have multiple people interested in maintaining large
> sets of ebuilds.
For multiple packages, yes; but I don't see any gain for a single one.
> If nothing else, they make life easier for bug wranglers, especially
> when you have >2 maintainers.
Not really; even if you list a ton of maintainers, it takes one
shortcut key press on a bug page to add all of them right away.
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-11-09 17:48 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 [this message]
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
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=20131109184725.0b61ac06@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=wired@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