From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Stephen Jolley <sjolley.yp.pm@gmail.com>
Cc: Yocto-mailing-list <yocto@lists.yoctoproject.org>,
",openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
yocto-status@lists.yoctoproject.org
Subject: Re: [OE-core] Yocto Project Status 9 April 2024 (WW15)
Date: Wed, 10 Apr 2024 11:06:22 +0200 [thread overview]
Message-ID: <CANNYZj90YBS2YviX2CUwaJoEN_dwRK3MyGZ7LGmKmuTLuMf7Zg@mail.gmail.com> (raw)
In-Reply-To: <CAK5yBb8v4nejwGYPj3YYRQnz7xDeL_3v=dk3_RkrvJCaysPdqA@mail.gmail.com>
On Tue, 9 Apr 2024 at 16:55, Stephen Jolley <sjolley.yp.pm@gmail.com> wrote:
> We received some disappointing feedback from a key organization in the RISC-V ecosystem that the Yocto Project was not important and not worth funding. We will take this feedback into account.
Can anything else be disclosed about this?
Alex
prev parent reply other threads:[~2024-04-10 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 14:55 Yocto Project Status 9 April 2024 (WW15) Stephen K Jolley
2024-04-10 9:06 ` Alexander Kanavin [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=CANNYZj90YBS2YviX2CUwaJoEN_dwRK3MyGZ7LGmKmuTLuMf7Zg@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sjolley.yp.pm@gmail.com \
--cc=yocto-status@lists.yoctoproject.org \
--cc=yocto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).