From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] Portage-ng / Lost ebuilds?
Date: Fri, 5 Dec 2003 09:42:04 +0100 [thread overview]
Message-ID: <200312050942.05159.pauldv@gentoo.org> (raw)
In-Reply-To: <1070594948.24977.10.camel@gen2rd.web>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 528 bytes --]
On Friday 05 December 2003 04:29, rd wrote:
> Referring to the following below, is portage-ng going to address this
> very serious issue as related to applying JUST security updates to
> "stable" production gentoo boxes?
>
This is an issue that will hopefully be addressed in the future, but it has
little to do with portage. We will look at providing releases that we will
only provide security fixes on.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-05 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 3:29 [gentoo-portage-dev] Portage-ng / Lost ebuilds? rd
2003-12-05 8:42 ` Paul de Vrieze [this message]
2003-12-06 4:33 ` rd
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=200312050942.05159.pauldv@gentoo.org \
--to=pauldv@gentoo.org \
--cc=gentoo-portage-dev@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