From: "cp0613" <cp0613@linux.alibaba.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe] [PATCH] rust-snapshot:add riscv64 toolchains
Date: Mon, 21 Nov 2022 03:17:40 -0800 [thread overview]
Message-ID: <24762.1669029460425937709@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj_g16GDm-WcGW6pQjdhkJ0_49373e4DXEZwF5Szi1HHdw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 142 bytes --]
Yes, I agree with your point of view and understand the impact of this,
the current time may not be mature enough,
thanks for your review.
[-- Attachment #2: Type: text/html, Size: 150 bytes --]
prev parent reply other threads:[~2022-11-21 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 10:11 [meta-oe] [PATCH] rust-snapshot:add riscv64 toolchains cp0613
2022-11-19 10:21 ` [OE-core] " Alexander Kanavin
2022-11-19 12:51 ` cp0613
2022-11-20 10:49 ` [OE-core] " Alexander Kanavin
2022-11-21 1:40 ` cp0613
2022-11-21 11:08 ` [OE-core] " Alexander Kanavin
2022-11-21 11:17 ` cp0613 [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=24762.1669029460425937709@lists.openembedded.org \
--to=cp0613@linux.alibaba.com \
--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