From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: DORA RFC: FILESOVERIDES in dora
Date: Mon, 18 Nov 2013 20:46:02 +0800 [thread overview]
Message-ID: <528A0C0A.2090008@windriver.com> (raw)
In-Reply-To: <CAJTo0LZWNbMFA1ogn2W7dvxtXh31LovO9QbYKcQsGpTR7C6KCg@mail.gmail.com>
On 11/18/2013 07:15 PM, Burton, Ross wrote:
> On 18 November 2013 11:10, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> a) Revert the change in the branch. Anyone who adapted to the correct
>> behaviour on the branch would need to revert those changes
>
> As there hasn't been a .1 of Dora yet this only impacts people who
> have been tracking git, so I think it's probably best to apologise for
> this merge and revert it, on the grounds that it's a serious behaviour
> change.
>
I'm afraid that the problem is it doesn't work well after revert the patch,
either, as the patch says:
Currently the overrides are being applied backwards. This means something
which is platform specific is overriding something which is machine specific
which is clearly not intended.
I don't know how many layers are affected, I've tested the current dora branch
in the local autobuilder, didin't find any errors.
// Robert
> Ross
>
>
next prev parent reply other threads:[~2013-11-18 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 11:10 DORA RFC: FILESOVERIDES in dora Richard Purdie
2013-11-18 11:15 ` Burton, Ross
2013-11-18 11:18 ` Otavio Salvador
2013-11-18 12:46 ` Robert Yang [this message]
2013-11-18 14:25 ` Burton, Ross
2013-11-18 15:37 ` Martin Jansa
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=528A0C0A.2090008@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox