On Thu, 2020-05-21 at 17:05 -0700, Khem Raj wrote:
> On Thu, May 21, 2020 at 4:49 PM Mittal, Anuj <anuj.mit...@intel.com>
> wrote:
> > On Thu, 2020-05-21 at 19:37 +0200, Martin Jansa wrote:
> > > On Thu, May 21, 2020 at 6:16 PM Khem Raj <raj.k...@gmail.com>
> > > wrote:
> > > > Now that they uses -mcpu, its better to have tune specific
> > > > build
> > > > directories, since aarch64 wont be appropriate any longer
> > > 
> > > I agree with Steve that this is a bit invasive for stable branch,
> > > but
> > > on the other hand it's long overdue and if we don't improve it in
> > > LTS
> > > branch then many people will need to carry local work arounds for
> > > multi-machine builds. +1 from me.
> > > 
> > 
> > But this is against the LTS/Stable branch policy. What is the point
> > of
> > having a policy if we are going to keep making exceptions? There'd
> > be
> > other changes as well for which people might be carrying work-
> > arounds.
> > Would we be willing to make exceptions for all?
> > 
> 
> Thanks for bringing this up. Policy exceptions are not common but
> they

That's two exceptions in a week.

I am not against the change but I think the policy document should be
modified to define how exceptions should/will be handled. 

> are not absent either
> hence context is important for such changes, I am definitely
> interested to hear
> about how it is going to affect arm64 users at this early stage of
> release. 

The release has been made and I think the branch is assumed to be
stable from the time it was released and policy should be applied?
There's no early release stage defined where-in such changes would be
acceptable.

Thanks,

Anuj
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#138565): 
https://lists.openembedded.org/g/openembedded-core/message/138565
Mute This Topic: https://lists.openembedded.org/mt/74379085/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to