From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Thomas Renninger <trenn@suse.de>
Cc: cpufreq@vger.kernel.org
Subject: Re: [PATCH 1/3] cpupowerutuils: Jump to version 010
Date: Sat, 2 Oct 2010 12:34:44 +0200 [thread overview]
Message-ID: <20101002103444.GA2002@comet.dominikbrodowski.net> (raw)
In-Reply-To: <1285672408-26839-2-git-send-email-trenn@suse.de>
On Tue, Sep 28, 2010 at 01:13:26PM +0200, Thomas Renninger wrote:
> Jump from version 008 to 010.
> Theoretically there could still be an cpufrequtils update to 009, but even
> if not, having a gap to show there were quite some changes is a good idea.
NAK. VERSION is only updated to a new major version on a release. I changed
VERSION to 9p1 (for 9-pre1) instead.
Best,
Dominik
next prev parent reply other threads:[~2010-10-02 10:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 15:30 Rename cpufrequtils into cpupowerutils and provide some basic cpuidle functionality Thomas Renninger
2010-09-23 15:30 ` [PATCH 1/4] cpufrequtils: Prepare for non-cpufreq related power features by renaming files Thomas Renninger
2010-09-23 15:30 ` [PATCH 2/4] cpufrequtils: Add cpuidle-info tool with some cstate library functions Thomas Renninger
2010-09-23 15:30 ` [PATCH 3/4] cpufrequtils: Rename libcpufreq to libcpupower Thomas Renninger
2010-09-23 15:30 ` [PATCH 4/4] cpufrequtils: Rename the project/package into cpupowerutils Thomas Renninger
2010-09-25 12:37 ` Rename cpufrequtils into cpupowerutils and provide some basic cpuidle functionality Dominik Brodowski
2010-09-28 11:06 ` Thomas Renninger
2010-09-28 11:13 ` [PATCH 1/3] cpupowerutuils: Jump to version 010 Thomas Renninger
2010-10-02 10:34 ` Dominik Brodowski [this message]
2010-09-28 11:13 ` [PATCH 2/3] cpupowerutils: Use sbindir for binaries that need root privileges Thomas Renninger
2010-10-02 10:35 ` Dominik Brodowski
2010-09-28 11:13 ` [PATCH 3/3] cpupowerutils: cpufreq-bench must link against libcpupower Thomas Renninger
2010-10-02 10:36 ` Dominik Brodowski
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=20101002103444.GA2002@comet.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=cpufreq@vger.kernel.org \
--cc=trenn@suse.de \
/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