From: Sam James <sam@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Last rites: app-backup/mkstage4
Date: Fri, 02 Aug 2024 21:37:19 +0100 [thread overview]
Message-ID: <87zfpu1x1c.fsf@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 225 bytes --]
# Sam James <sam@gentoo.org> (2024-08-02)
# Unreliable software, unmaintained in Gentoo. Having it in the main
# repositories may give users an impression of it being a safe tool.
# Removal on 2024-09-01.
app-backup/mkstage4
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
reply other threads:[~2024-08-02 20:37 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=87zfpu1x1c.fsf@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