From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Last rites: sys-process/vixie-cron
Date: Wed, 11 Sep 2019 14:01:31 +0200 [thread overview]
Message-ID: <bbd93ee73fa0d546e33e19f660c26c65988ad44d.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
# Michał Górny <mgorny@gentoo.org> (2019-09-11)
# Unmaintained. Ancient. Carries a lot of patches, and has even more
# bugs reported. Last rites were cancelled due to Gentoo/FreeBSD 1 year
# ago but that project is dead nowadays. Many alternatives exist,
# sys-process/cronie is probably the closest one (it's a fork).
# Removal in 30 days. Bug #693946.
sys-process/vixie-cron
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next reply other threads:[~2019-09-11 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 12:01 Michał Górny [this message]
2019-09-11 13:53 ` [gentoo-dev] Last rites: sys-process/vixie-cron Ralph Seichter
-- strict thread matches above, loose matches on Subject: below --
2018-09-20 9:17 Mikle Kolyada
2018-09-20 21:07 ` Thomas Deutschmann
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=bbd93ee73fa0d546e33e19f660c26c65988ad44d.camel@gentoo.org \
--to=mgorny@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