public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
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 12:14:19 +0100	[thread overview]
Message-ID: <1164712459.4656.253.camel@queen.suse.de> (raw)
In-Reply-To: <456C0E5A.5090703@linux.intel.com>

On Tue, 2006-11-28 at 13:24 +0300, Alexey Starikovskiy wrote:
> 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?
It's not the two names, it simply makes no sense to provide two
utilities which do the same.

Why do you want to do that?

You have other params, other output, double amount of bug fixing or
feature enhancements work. I only see cons not one single pro argument
to do so.

> pmtools used to be complete in sense it was able to decode that was it 
> has produced, and it will remain complete.
But why not just move/copy Robert's acpixtract, it's already well
tested?
It does not include any APCICA stuff and changing the license shouldn't
be a problem for you...

   Thomas


  reply	other threads:[~2006-11-28 11:14 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
2006-11-28 11:14     ` Thomas Renninger [this message]
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=1164712459.4656.253.camel@queen.suse.de \
    --to=trenn@suse.de \
    --cc=alexey.y.starikovskiy@linux.intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=robert.moore@intel.com \
    /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