From: Alexandra Yates <alexandra.yates at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] Complete build options for Pthread API
Date: Thu, 30 Oct 2014 19:34:56 -0700 [thread overview]
Message-ID: <63912.10.255.85.192.1414722896.squirrel@linux.intel.com> (raw)
In-Reply-To: CAG27Bk2jDUn-1SoWqFQhb2ac22vdrpTBax8VU_Gv+e02Dw2_rw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
All,
> On 22 October 2014 13:41, Sergey Senozhatsky
> <sergey.senozhatsky(a)gmail.com> wrote:
>> m4/* files are host-specific. they should never be part
>> of the source code or a package.
>
> I would not say it so strongly. There are plenty of projects that have
> files in m4 directory. Here's couple.
>
> http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=tree;f=m4
> https://github.com/karelzak/util-linux/tree/master/m4
>
> But if powertop does not want to mix files autotools generate with own
> files then an alternative path is needed. Perhaps powertop/m4/ could
> be used. That would leave door open to various other project local
> purposes as well files. What ever is done a maintainer decision is
> needed. In best case the decision should be documented to
> powertop/readmes/project_files.txt or something like that.
>
> --
> Sami Kerola
> http://www.iki.fi/kerolasa/
> _______________________________________________
> PowerTop mailing list
> PowerTop(a)lists.01.org
> https://lists.01.org/mailman/listinfo/powertop
>
I agree with Sergei, we use m4/* for generating our configuration files only.
Thank you,
Alexandra.
next reply other threads:[~2014-10-31 2:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 2:34 Alexandra Yates [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-01 8:15 [Powertop] Complete build options for Pthread API SF Markus Elfring
2014-10-31 18:01 Alexandra Yates
2014-10-31 10:20 SF Markus Elfring
2014-10-31 10:01 Sami Kerola
2014-10-31 3:35 Alexandra Yates
2014-10-25 10:18 Sami Kerola
2014-10-25 8:58 Sergey Senozhatsky
2014-10-22 14:33 Sami Kerola
2014-10-22 12:41 Sergey Senozhatsky
2014-10-22 9:41 Sami Kerola
2014-10-20 4:44 SF Markus Elfring
2014-10-19 18:18 Sami Kerola
2014-10-19 11:30 SF Markus Elfring
2014-10-18 22:57 Sami Kerola
2014-10-18 19:20 SF Markus Elfring
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=63912.10.255.85.192.1414722896.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.