From: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
To: trenn@suse.de
Cc: "Moore, Robert" <robert.moore@intel.com>,
"Brown, Len" <len.brown@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: new pmtools available for testing
Date: Tue, 28 Nov 2006 13:24:26 +0300 [thread overview]
Message-ID: <456C0E5A.5090703@linux.intel.com> (raw)
In-Reply-To: <1164708222.4656.203.camel@queen.suse.de>
Thomas Renninger wrote:
> On Mon, 2006-11-27 at 10:13 -0800, Moore, Robert wrote:
>
>> I don't know what's going on here.
>>
>> I wrote acpixtract in C in order to get away from Perl and Perl issues.
>>
>> I certainly hope that we don't have yet another version of acpixtract.
>>
> Second.
> Better remove this one soon. People are packing Len's pmtools. As soon
> as it's spread confusion and maintenance work will grow.
>
There was no confusion between two utilities with the same name, and now you claim to have lost between two with different names, how so?
pmtools used to be complete in sense it was able to decode that was it
has produced, and it will remain complete.
Thanks,
Alex.
next prev parent reply other threads:[~2006-11-28 10:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 18:13 new pmtools available for testing Moore, Robert
2006-11-28 10:03 ` Thomas Renninger
2006-11-28 10:24 ` Alexey Starikovskiy [this message]
2006-11-28 11:14 ` Thomas Renninger
2006-11-28 14:00 ` Alexey Starikovskiy
2006-11-29 16:31 ` Bruno Ducrot
-- strict thread matches above, loose matches on Subject: below --
2006-12-12 22:35 Moore, Robert
2006-11-21 18:24 Alexey Starikovskiy
2006-11-21 18:27 ` Alexey Starikovskiy
2006-11-22 13:55 ` Thomas Renninger
2006-11-22 14:36 ` Alexey Starikovskiy
2006-11-22 15:25 ` Thomas Renninger
2006-11-22 16:40 ` Alexey Starikovskiy
2006-12-10 15:50 ` Mattia Dongili
2006-12-10 17:11 ` Alexey Starikovskiy
2006-12-11 18:20 ` Len Brown
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=456C0E5A.5090703@linux.intel.com \
--to=alexey.y.starikovskiy@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=robert.moore@intel.com \
--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