From: David Seifert <soap@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: mgorny@gentoo.org
Subject: Re: [gentoo-dev] Last rites: unmaintained Go packages with license issues
Date: Wed, 04 Dec 2019 01:05:43 +0100 [thread overview]
Message-ID: <055604e3a0f63ebe9ac83b93cdf995fe029ea6bb.camel@gentoo.org> (raw)
In-Reply-To: <20191203184255.GA15232@whubbs1.dev.av1.gaikai.org>
On Tue, 2019-12-03 at 12:42 -0600, William Hubbs wrote:
> I'm not sure what happened to my last message, so I'm trying again.
>
> On Sun, Dec 01, 2019 at 10:23:12PM +0100, Michał Górny wrote:
> > app-admin/docker-bench
> > app-emulation/cadvisor
> > app-emulation/reg
> > app-metrics/alertmanager
> > app-metrics/bind_exporter
> > app-metrics/blackbox_exporter
> > app-metrics/burrow_exporter
> > app-metrics/elasticsearch_exporter
> > app-metrics/mongodb_exporter
> > app-metrics/nginx-vts-exporter
> > app-metrics/node_exporter
> > app-metrics/openvpn_exporter
> > app-metrics/postfix_exporter
> > app-metrics/postgres_exporter
> > app-metrics/prometheus
> > app-metrics/snmp_exporter
> > app-metrics/vault_exporter
> > dev-util/drone
> > dev-util/drone-cli
> > sys-auth/docker_auth
>
> My employer has an interest in all of these, so please unmask and
> assign
> to me.
>
> Thanks,
>
> William
>
Re-hashing what we discussed on IRC:
In order to facilitate your workflow, you may unmask these packages,
but QA reserves the right to mask them again in 2 weeks if the
licensing issues have not been resolved.
Regards
David
next prev parent reply other threads:[~2019-12-04 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 21:23 [gentoo-dev] Last rites: unmaintained Go packages with license issues Michał Górny
2019-12-03 16:38 ` William Hubbs
2019-12-03 21:48 ` Mike Gilbert
2019-12-03 23:46 ` William Hubbs
2019-12-03 23:46 ` David Seifert
2019-12-03 18:42 ` William Hubbs
2019-12-04 0:05 ` David Seifert [this message]
2019-12-04 0:26 ` [gentoo-dev] " Holger Hoffstätte
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=055604e3a0f63ebe9ac83b93cdf995fe029ea6bb.camel@gentoo.org \
--to=soap@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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