From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Question, Portage QOS v2
Date: Fri, 10 Jan 2014 18:21:12 +0000 [thread overview]
Message-ID: <20140110182112.100e8953@googlemail.com> (raw)
In-Reply-To: <52d031ec.e48b700a.2293.ffffb513@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
On Fri, 10 Jan 2014 21:46:18 +0400
Igor <lanthruster@gmail.com> wrote:
> And one more goal - without PortageQOS you're forever stuck with
> the legacy portage design.
>
> If the team ever decides to change Portage you'll need feedback
> on how the new portage works to patch it quickly in case there are
> troubles. It's too risky to touch portage right now. Everyone
> understands that this is a kamikaze job.
Uh, no. We already know lots of things that are wrong with the Portage
design. We also know how to fix those things. Neither of those is the
sticking point.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2014-01-10 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 17:18 [gentoo-dev] Question, Portage QOS v2 Igor
2014-01-10 17:20 ` Andreas K. Huettel
2014-01-10 17:39 ` Igor
2014-01-10 17:46 ` Igor
2014-01-10 18:21 ` Ciaran McCreesh [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=20140110182112.100e8953@googlemail.com \
--to=ciaran.mccreesh@googlemail.com \
--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