From: Anton Mikanovich <amikan@ilbers.de>
To: henning.schild@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCHv3 0/3] sstate bug fix
Date: Mon, 21 Feb 2022 12:23:03 +0300 [thread overview]
Message-ID: <84366b7e-2fc1-a2df-64f5-9dc0eaa1f73b@ilbers.de> (raw)
In-Reply-To: <20220204164124.10396-1-henning.schild@siemens.com>
4.02.22 19:41, henning.schild@siemens.com wrote:
> changes since v2:
> - add p3
>
> changes since v1:
> - add p2
> - fix typo in p1
> - move code around in p1, later touched again in p2
>
> This is just a single patch but i think it fixes bugs and should be
> considered before a release ... i usually do not do cover letters for
> single patches. So here i still do it to point out that it might be
> important.
>
> Henning Schild (3):
> sstate: change rootfs task to cache
> sstate: fix task order and deps
> buildchroot: make function buildchroot_install_files idempotent
>
> meta/classes/rootfs.bbclass | 26 +++++++++----------
> .../buildchroot/buildchroot.inc | 2 +-
> 2 files changed, 14 insertions(+), 14 deletions(-)
>
Applied to next, thanks.
prev parent reply other threads:[~2022-02-21 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 16:41 henning.schild
2022-02-04 16:41 ` [PATCHv3 1/3] sstate: change rootfs task to cache henning.schild
2022-02-04 16:41 ` [PATCHv3 2/3] sstate: fix task order and deps henning.schild
2022-02-04 16:41 ` [PATCHv3 3/3] buildchroot: make function buildchroot_install_files idempotent henning.schild
2022-02-15 10:08 ` [PATCHv3 0/3] sstate bug fix Schmidt, Adriaan
2022-02-16 14:08 ` Anton Mikanovich
2022-02-21 9:23 ` Anton Mikanovich [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=84366b7e-2fc1-a2df-64f5-9dc0eaa1f73b@ilbers.de \
--to=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox