From: Adrian Bunk <bunk@stusta.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] Future of sato and X in oe-core
Date: Tue, 11 Feb 2020 16:13:47 +0200 [thread overview]
Message-ID: <20200211141347.GB3234@localhost> (raw)
In-Reply-To: <CANNYZj_v9=Ys-NXqHWXY42dZqT95+LxcRUqSRKcyy6pMz-Y01g@mail.gmail.com>
On Tue, Feb 11, 2020 at 03:01:20PM +0100, Alexander Kanavin wrote:
> Specifically (sorry for the rapid-followup), I think the main value
> proposition of core is integration and testing of various language
> toolchains and core libraries. UIs in embedded space can mean pretty much
> anything, and so I'd leave that to specialised layers.
That's actually quite different from your original email.
Your original email raised the problem that X might start to bitrot
after the end of support for RHEL 8 in the year 2029 (sic).
What functionality should be in core for users/demo/QA/...
is not strictly related to X versus Wayland.
> Alex
cu
Adrian
next prev parent reply other threads:[~2020-02-11 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 12:49 Future of sato and X in oe-core Alexander Kanavin
2020-02-11 13:53 ` [Openembedded-architecture] " Adrian Bunk
2020-02-11 13:57 ` Alexander Kanavin
2020-02-11 14:01 ` Alexander Kanavin
2020-02-11 14:13 ` Adrian Bunk [this message]
2020-02-11 14:35 ` Alexander Kanavin
2020-02-11 15:02 ` Adrian Bunk
2020-02-11 15:58 ` Mark Hatle
2020-02-11 17:46 ` Alexander Kanavin
2020-02-16 16:38 ` Alexander Kanavin
2020-02-11 15:54 ` Mark Hatle
2020-02-11 14:05 ` Josef Holzmayr
2020-02-11 17:53 ` Richard Purdie
2020-02-11 17:59 ` Martin Jansa
2020-02-11 18:06 ` Alexander Kanavin
2020-02-12 11:40 ` Adrian Bunk
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=20200211141347.GB3234@localhost \
--to=bunk@stusta.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox