All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Stefan Herbrechtsmeier
	<stefan.herbrechtsmeier-oss@weidmueller.com>,
	 Alexander Kanavin <alex@linutronix.de>,
	Michael Opdenacker <michael.opdenacker@bootlin.com>,
	 Randy MacLeod <randy.macleod@windriver.com>,
	Sergey Bostandzhyan <jin@mediatomb.cc>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 01/13] cargo-update-recipe-crates.bbclass: add a class to generate SRC_URI crate lists from Cargo.lock
Date: Fri, 9 Dec 2022 15:43:13 +0100	[thread overview]
Message-ID: <CANNYZj-BDoPzV5qNLKafbr-0s7PLU2WCvmdA1OfZhW2qxqq1Gg@mail.gmail.com> (raw)
In-Reply-To: <7f51955aada8f9e74322aa0ad15f21b9985d993d.camel@linuxfoundation.org>

On Fri, 9 Dec 2022 at 13:01, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> I'd note Alex has another patch which has been sitting for months
> unmerged as it is in my "high risk" to the project category. I suspect
> that one will not actually merge but I need to find the time to explain
> why, right now it is more based on a feeling it is the wrong direction.

I'd be happy to be 'course corrected' on oe-setup-build, I personally
feel it does more 'guessing' than I'm comfortable with but I can't
figure out a better way to handle things. The problems it's aiming to
address are real, so it shouldn't be formally rejected without a plan.

Alex


  reply	other threads:[~2022-12-09 14:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 11:47 [PATCH 01/13] cargo-update-recipe-crates.bbclass: add a class to generate SRC_URI crate lists from Cargo.lock Alexander Kanavin
2022-10-31 11:47 ` [PATCH 02/13] python3-bcrypt: convert to use cargo-update-recipe-crates class Alexander Kanavin
2022-10-31 11:47 ` [PATCH 03/13] python3-cryptography: convert to " Alexander Kanavin
2022-10-31 11:47 ` [PATCH 04/13] groff: submit patches upstream Alexander Kanavin
2022-10-31 11:47 ` [PATCH 05/13] tcl: correct patch status Alexander Kanavin
2022-10-31 11:47 ` [PATCH 06/13] tcl: correct upstream version check Alexander Kanavin
2022-10-31 11:47 ` [PATCH 07/13] lttng-tools: submit determinism.patch upstream Alexander Kanavin
2022-10-31 11:47 ` [PATCH 08/13] cmake: drop qt4 patches Alexander Kanavin
2022-10-31 11:47 ` [PATCH 09/13] kea: submit patch upstream Alexander Kanavin
2022-10-31 11:47 ` [PATCH 10/13] argp-standalone: replace with a maintained fork Alexander Kanavin
2022-10-31 11:47 ` [PATCH 11/13] ovmf: correct patches status Alexander Kanavin
2022-10-31 11:47 ` [PATCH 12/13] go: submit patch upstream Alexander Kanavin
2022-10-31 21:55   ` [OE-core] " Richard Purdie
2022-10-31 22:17     ` Alexander Kanavin
2022-10-31 11:47 ` [PATCH 13/13] libffi: " Alexander Kanavin
2022-12-06 23:04 ` [OE-core] [PATCH 01/13] cargo-update-recipe-crates.bbclass: add a class to generate SRC_URI crate lists from Cargo.lock Randy MacLeod
2022-12-07  0:20   ` Sergey 'Jin' Bostandzhyan
2022-12-07  8:53     ` Alexander Kanavin
2022-12-07 15:28       ` Stefan Herbrechtsmeier
2022-12-07 16:21         ` Alexander Kanavin
2022-12-09 10:39           ` Stefan Herbrechtsmeier
2022-12-09 12:01             ` Richard Purdie
2022-12-09 14:43               ` Alexander Kanavin [this message]
2022-12-09 14:58                 ` Richard Purdie
2022-12-09 15:18               ` Stefan Herbrechtsmeier
2022-12-09 12:09             ` Alexander Kanavin
2022-12-12 14:18               ` Stefan Herbrechtsmeier
2022-12-12 15:00                 ` Alexander Kanavin

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=CANNYZj-BDoPzV5qNLKafbr-0s7PLU2WCvmdA1OfZhW2qxqq1Gg@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=jin@mediatomb.cc \
    --cc=michael.opdenacker@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=stefan.herbrechtsmeier-oss@weidmueller.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.