From: Alexandra Yates <alexandra.yates at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [PATCH] powertop: update build instructions
Date: Fri, 22 Aug 2014 14:08:54 -0700 [thread overview]
Message-ID: <49498.10.7.198.163.1408741734.squirrel@linux.intel.com> (raw)
In-Reply-To: CABsxX9KLKUfHjC2AJqbuomwzuhh7i08gFuKWvA-0rBA8JKzBoQ@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]
> On Sun, Jul 13, 2014 at 12:26 AM, Sergey Senozhatsky
> <sergey.senozhatsky(a)gmail.com> wrote:
>> On (07/13/14 12:06), Mohammad Merajul Islam Molla wrote:
>>> update powertop build instuctions in README file.
>>>
>>> Signed-off-by: Mohammad Merajul Islam Molla <meraj.enigma(a)gmail.com>
>>> ---
>>> README | 7 ++++---
>>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/README b/README
>>> index cd38cc5..efe95c3 100644
>>> --- a/README
>>> +++ b/README
>>> @@ -2,9 +2,10 @@
>>> ------------------------------
>>>
>>> To build and install PowerTOP type the following commands,
>>> - ./configure
>>> - ./make
>>> - ./make install
>>> + autoreconf -sfi
>>
>> we have autogen.sh to deal with autoreconf. let's recommend to use
>> it instead of direct autoreconf.
>
> These instructions are currently correct when people download the
> published tarballs, and this change would make them incorrect, or
> unnecessarily make people rerun autoconf & friends at the least.
>
> I suggest you document both build cases, e.g. some text for people who
> build from git sources, vs. those folks who do distribution
> integration and never build from git.
>
> Cheers,
>
> Auke
> _______________________________________________
> PowerTop mailing list
> PowerTop(a)lists.01.org
> https://lists.01.org/mailman/listinfo/powertop
>
Hi Mohammad,
Please send the updated readme patch to match Auke's feedback: "... I
suggest you document both build cases, e.g. some text for people who build
from git sources, vs. those folks who do distribution integration and
never build from git...".
Please create your patches editing your subject prefix and the version
number of this patch. That facilitate accepting your patches.
git format-patch --cover-letter --subject-prefix="PATCH Vn" ...
Thank you,
Alexandra.
next reply other threads:[~2014-08-22 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 21:08 Alexandra Yates [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-14 19:55 [Powertop] [PATCH] powertop: update build instructions Kok, Auke-jan H
2014-07-13 7:26 Sergey Senozhatsky
2014-07-13 6:06 Mohammad Merajul Islam Molla
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=49498.10.7.198.163.1408741734.squirrel@linux.intel.com \
--to=powertop@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.