From: "Otavio Salvador" <otavio.salvador@ossystems.com.br>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Khem Raj <raj.khem@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Ross Burton <ross.burton@intel.com>
Subject: Re: [OE-core] [PATCH] binutils: Pregenerate autoconf files
Date: Thu, 26 Mar 2020 09:56:01 -0300 [thread overview]
Message-ID: <CAP9ODKomZjQ30ZGSnt3MpHvBQPHSfj=71tBQ+VxzaVOwLLTrZw@mail.gmail.com> (raw)
In-Reply-To: <9c14fe5a594e1edd4cb678340ec27859ba9df864.camel@linuxfoundation.org>
On Thu, Mar 26, 2020 at 9:45 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Wed, 2020-03-25 at 16:16 -0700, Khem Raj wrote:
...
> I'm also worried about patches which touch both configure and
> configure.ac since the timestamp changes can cause things to autoreconf
> even when we're trying to avoid that. As such this is actually quite a
> risky change given past bad experiences :(
>
> I'm not completely against it but I am worried.
+1
I also prefer to generate them. The patches are easier to upgrade and
allow for easier fixes, as mentioned.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2020-03-26 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 23:16 [PATCH] binutils: Pregenerate autoconf files Khem Raj
2020-03-26 12:45 ` [OE-core] " Richard Purdie
2020-03-26 12:56 ` Otavio Salvador [this message]
2020-03-26 17:03 ` Khem Raj
2020-03-26 18:29 ` Khem Raj
2020-03-27 0:57 ` Khem Raj
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='CAP9ODKomZjQ30ZGSnt3MpHvBQPHSfj=71tBQ+VxzaVOwLLTrZw@mail.gmail.com' \
--to=otavio.salvador@ossystems.com.br \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@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 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.