All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwan <M.Schwan@phytec.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] cargo-update-recipe-crates: Don't fail for partially empty Cargo.lock
Date: Thu, 11 Dec 2025 13:23:31 +0000	[thread overview]
Message-ID: <cd485373cfa253d77f0e94ce6434cf90f61bc715.camel@phytec.de> (raw)
In-Reply-To: <CANNYZj96iASKujEQRjxVn9AMSRjHV7ep=oh6JbaZw+kWnOOsqQ@mail.gmail.com>

On Tue, 2025-11-25 at 11:23 +0100, Alexander Kanavin wrote:
> On Tue, 25 Nov 2025 at 10:01, Martin Schwan via
> lists.openembedded.org
> <m.schwan=phytec.de@lists.openembedded.org> wrote:
> > 
> > Do not fail if only some Cargo.lock files are empty. Only fail, if
> > there
> > are absolutely no dependencies found in any Cargo.lock.
> 
> ...
> 
> > While at it, restructure do_update_crates() to be a real Python
> > function
> > and use the corresponding code directly inline.
> 
> This, as a diff on the mailing list, is incredibly hard to review,
> and
> needs to be split up. Refactoring in one commit (explaining the
> benefits), functional changes in another please. Even better if you
> can split things further, and explain what the particular
> modifications are (rather than use terms like 'restructure').

Thanks for the feedback. Admittedly, I was a bit lazy with this one, as
the changes were quite interwoven. I'll send a v2 and split things up,
as best as I can.

Regards,
Martin

> 
> Aelx

  reply	other threads:[~2025-12-11 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25  9:00 [PATCH] cargo-update-recipe-crates: Don't fail for partially empty Cargo.lock Martin Schwan
2025-11-25 10:23 ` [OE-core] " Alexander Kanavin
2025-12-11 13:23   ` Martin Schwan [this message]
2025-11-25 14:20 ` Clayton Casciato

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=cd485373cfa253d77f0e94ce6434cf90f61bc715.camel@phytec.de \
    --to=m.schwan@phytec.de \
    --cc=alex.kanavin@gmail.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 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.