From: Henrik Brix Andersen <brix@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Deprecating sys-power/speedfreq
Date: Mon, 25 Apr 2005 22:51:31 +0200 [thread overview]
Message-ID: <1114462291.13969.8.camel@sponge.fungus> (raw)
In-Reply-To: <426D545B.5000309@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
On Mon, 2005-04-25 at 23:34 +0300, Alin Nastac wrote:
> If it is superseded by cpufreqd, why not removing it from the tree and
> append "move sys-power/speedfreq sys-power/cpufreqd" line in
> updates/2Q-2005?
Because 'move' is for renaming packages?
./Brix
--
Henrik Brix Andersen <brix@gentoo.org>
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-25 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 19:55 [gentoo-dev] Deprecating sys-power/speedfreq Henrik Brix Andersen
2005-04-25 20:09 ` Greg Hasseler
2005-04-25 23:30 ` Henrik Brix Andersen
2005-04-26 20:24 ` Greg Hasseler
2005-05-07 17:38 ` Henrik Brix Andersen
2005-04-25 20:34 ` Alin Nastac
2005-04-25 20:51 ` Henrik Brix Andersen [this message]
2005-04-25 21:57 ` Alin Nastac
2005-04-25 23:37 ` Jason Stubbs
2005-04-26 1:07 ` Donnie Berkholz
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=1114462291.13969.8.camel@sponge.fungus \
--to=brix@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