From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev-announce] Last rites: app-editors/emacs:21 and app-editors/emacs:22
Date: Thu, 8 May 2014 14:03:05 +0200 [thread overview]
Message-ID: <21355.29305.932337.748076@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20199.40811.722548.3069@a1i15.kph.uni-mainz.de>
# Ulrich Müller <ulm@gentoo.org> (08 May 2014)
# SLOTs 21 and 22 of app-editors/emacs, corresponding to
# GNU Emacs versions 21.4 and 22.3. These versions were
# released in February 2005 and September 2008, respectively.
# Please upgrade to >=app-editors/emacs-23 and update your
# Emacs Lisp packages with emacs-updater.
# Multiple security issues with temporary files, bug 509830.
# Masked since 13 Dec 2011, removal at 07 Jun 2014. Bug 394589.
=app-editors/emacs-21*
=app-editors/emacs-22*
~virtual/emacs-21
~virtual/emacs-22
prev parent reply other threads:[~2014-05-08 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 16:44 [gentoo-dev-announce] Semi last rites: app-editors/emacs:21 and app-editors/emacs:22 Ulrich Mueller
2011-12-13 18:54 ` [gentoo-dev-announce] Last " Ulrich Mueller
2014-05-08 12:03 ` Ulrich Mueller [this message]
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=21355.29305.932337.748076@a1i15.kph.uni-mainz.de \
--to=ulm@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