From: "Denys Dmytriyenko" <denis@denix.org>
To: elberger@amazon.com
Cc: meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] Plan for meta-arago-distro (master)
Date: Tue, 17 Aug 2021 12:13:36 -0400 [thread overview]
Message-ID: <20210817161336.GD1528@denix.org> (raw)
In-Reply-To: <61eb847a-1f5d-a4b9-7300-1350005ebe2f@amazon.com>
On Tue, Aug 17, 2021 at 11:13:15AM -0400, elberger via lists.yoctoproject.org wrote:
> Hello,
>
> I need to use master branch due to MACHINE configuration
> availability only on master.
>
> However, the availability of new override syntax on
> meta-arago-distro emits the usual compatibility error. I noticed
> there is no master-next branch so this is probably the state of
> things.
>
> In such case
>
> 1/ is there a plan in motion to evolve meta-arago-distro and if so
> is there a rough timeline to have the syntax migrated
>
> or
>
> 2/ is there a possibility to take a PR - not sure how TI handles
> this since there is probably full regression testing done.
>
> thank you
Richard,
1. meta-ti mailing list is not the right place for meta-arago questions, but
anyway
2. meta-ti can be used on its own w/o meta-arago-distro with any other distro
and MACHINE configuration availability should not be blocked by meta-arago
3. override syntax conversion for meta-arago is still in progress and has been
blocked by meta-ti, which only got merged today
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
prev parent reply other threads:[~2021-08-17 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 15:13 Plan for meta-arago-distro (master) elberger
2021-08-17 16:13 ` Denys Dmytriyenko [this message]
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=20210817161336.GD1528@denix.org \
--to=denis@denix.org \
--cc=elberger@amazon.com \
--cc=meta-ti@lists.yoctoproject.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.