From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Last rites: dev-db/gigabase
Date: Sun, 17 Jul 2022 16:57:21 +0100 [thread overview]
Message-ID: <D1A5B4F1-1EC4-4B31-85B1-7C22314E1027@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 220 bytes --]
# Sam James <sam@gentoo.org> (2022-07-17)
# Code quality issues, out of date by several versions in Gentoo,
# unmaintained, and several open bugs: bugs #521272, #729684, #855230.
# Removal on 2022-08-17.
dev-db/gigabase
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
reply other threads:[~2022-07-17 19:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=D1A5B4F1-1EC4-4B31-85B1-7C22314E1027@gentoo.org \
--to=sam@gentoo.org \
--cc=gentoo-dev-announce@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