From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Last rites: unmaintained Go packages with license issues
Date: Tue, 3 Dec 2019 16:48:56 -0500 [thread overview]
Message-ID: <CAJ0EP41SRa-T_+YaC+_pC2s8PiMtyn9Nss_hJXV3SST9AGq05w@mail.gmail.com> (raw)
In-Reply-To: <20191203163817.GA14214@whubbs1.dev.av1.gaikai.org>
On Tue, Dec 3, 2019 at 11:38 AM William Hubbs <williamh@gentoo.org> wrote:
>
> 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 these, so I will take them. Please unmask
> and assign them to me.
I think it would be more appropriate for you to update/unmask them
yourself as you correct the license information.
next prev parent reply other threads:[~2019-12-03 21:49 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 [this message]
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
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=CAJ0EP41SRa-T_+YaC+_pC2s8PiMtyn9Nss_hJXV3SST9AGq05w@mail.gmail.com \
--to=floppym@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