From: Nikolai Kondrashov <spbnick@gmail.com>
To: Denys Fedoryshchenko <denys.f@collabora.com>, kernelci@lists.linux.dev
Subject: Re: KernelCI Weekly Newsletter (Week 2)
Date: Mon, 13 Jan 2025 13:23:29 +0200 [thread overview]
Message-ID: <962b6b41-3f21-4149-8869-562e11225681@gmail.com> (raw)
In-Reply-To: <8a2c4f7da3df1d3cd0e52c3bcc49f7fee9475b0c.camel@collabora.com>
Hi Denys,
Thank you for keeping posting these updates!
On 1/8/25 4:51 PM, Denys Fedoryshchenko wrote:
> 2. **KernelCI Development Roadmap**
> Through discussions with the community, we've identified a list of
> features and improvements for KernelCI.
> Please share your ideas or indicate if you'd like to contribute to
> any of these items.
> This is initial draft, and we will continue to refine the list.
Is there perhaps a doc or an issue where these are fleshed out with more details?
Nick
next prev parent reply other threads:[~2025-01-13 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 14:51 KernelCI Weekly Newsletter (Week 2) Denys Fedoryshchenko
2025-01-13 11:23 ` Nikolai Kondrashov [this message]
2025-01-15 11:37 ` Denys Fedoryshchenko
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=962b6b41-3f21-4149-8869-562e11225681@gmail.com \
--to=spbnick@gmail.com \
--cc=denys.f@collabora.com \
--cc=kernelci@lists.linux.dev \
/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