All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Randy MacLeod <randy.macleod@windriver.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] Merge meta-rust to oe-core
Date: Wed, 24 Feb 2021 09:39:04 +0000	[thread overview]
Message-ID: <a373f6be54f63987eb9cb0ce994b807fcca01062.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210224030201.349588-1-Randy.MacLeod@windriver.com>

On Tue, 2021-02-23 at 22:01 -0500, Randy MacLeod wrote:
> Clean-up the merge of meta-rust to oe-core by squashing most of the 
> meta-rust history so we are left with:
> 
>   35da4b252f rust: add a language demo image to test reproducibility
>   088374371b cargo/rust/rustfmt: exclude from world
>   7df10d2a22 meta-rust: merge commits
>   4187796cd6 rust: mv README.md to recipes-devtools/rust/README-rust.md
>   03b9c60ef4 meta-rust: move code to oe-core from meta-rust layer
>   2c62874204 libgit2: pull in updates from meta-oe
>   24cb3db88c libssh2: pull in additional commits from meta-oe
>   e9a0a3bad2 Add libgit2, libssh2 from meta-oe for rust
> 
> The full diffstat is below. (1)
> 
> I didn't really notice the scripts shown below since they are mostly harmless.
> I'll review them and remove them in v2 if they don't make sense for oe-core.

This is better, thanks. My feedback from a quick glance:

a) Need maintainer entries for the new recipes
b) The scripts in scripts/ look at the very least inappropriately named
   for OE-Core, I suspect we don't want/need those.
c) Not entirely sure about the languages demo image, its not how we test
   any other language
d) There aren't any tests in meta/lib/oeqa!
e) The rust README starts "This OpenEmbedded layer provides" and has a few other
   issues.

Cheers,

Richard



  parent reply	other threads:[~2021-02-24  9:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  3:01 Merge meta-rust to oe-core Randy MacLeod
2021-02-24  3:01 ` [PATCH 1/8] Add libgit2, libssh2 from meta-oe for rust Randy MacLeod
2021-02-24  3:01 ` [PATCH 2/8] libssh2: pull in additional commits from meta-oe Randy MacLeod
2021-02-24  3:01 ` [PATCH 3/8] libgit2: pull in updates " Randy MacLeod
2021-02-24  3:01 ` [PATCH 4/8] meta-rust: move code to oe-core from meta-rust layer Randy MacLeod
2021-02-24  3:01 ` [PATCH 5/8] rust: mv README.md to recipes-devtools/rust/README-rust.md Randy MacLeod
2021-02-24  3:01 ` [PATCH 6/8] meta-rust: merge commits Randy MacLeod
2021-02-24  3:02 ` [PATCH 7/8] cargo/rust/rustfmt: exclude from world Randy MacLeod
2021-02-24  3:02 ` [PATCH 8/8] rust: add a language demo image to test reproducibility Randy MacLeod
2021-02-24  9:39 ` Richard Purdie [this message]
2021-02-24 18:23   ` [OE-core] Merge meta-rust to oe-core Randy MacLeod
2021-02-24 20:26     ` Randy MacLeod
     [not found] ` <1666A58EF14596DD.29651@lists.openembedded.org>
2021-02-24 16:53   ` Richard Purdie

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=a373f6be54f63987eb9cb0ce994b807fcca01062.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    /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.