From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Alexander Kanavin" <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 1/3] selftest/sstatetests: add tests for 'bitbake -S printdiff'
Date: Fri, 27 Oct 2023 09:43:55 +0200 [thread overview]
Message-ID: <20231027094355.1a43f67b@booty> (raw)
In-Reply-To: <CANNYZj_6kh4bXP_bunqy1s178ZtArCgy=ms7+eTTYVY0G1H8jA@mail.gmail.com>
Hello Alex,
On Fri, 27 Oct 2023 07:29:28 +0200
"Alexander Kanavin" <alex.kanavin@gmail.com> wrote:
> On Thu, 26 Oct 2023 at 22:02, Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
> > Is this different from the series you sent on the 23rd? There is no
> > vN tag and no ChangeLog, so it's not obvious.
>
> Only the third patch should be different, and it has core-image-weston
> removed (as it was causing missing objects, as reported by you). I'll
> try to include changes under --- in each commit going forward.
That will be useful here, thanks! Without it, at least a v<N> in the
subject would be good to help keeping track of the current iteration.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-10-27 7:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 10:33 [PATCH 1/3] selftest/sstatetests: add tests for 'bitbake -S printdiff' Alexander Kanavin
2023-10-26 10:33 ` [PATCH 2/3] lib/oe/sstatesig.py: dump locked.sigs.inc only when explicitly asked via -S lockedsigs Alexander Kanavin
2023-10-26 10:33 ` [PATCH 3/3] selftest/sstatetests: add a test for CDN sstate cache Alexander Kanavin
2023-10-26 20:02 ` [OE-core] [PATCH 1/3] selftest/sstatetests: add tests for 'bitbake -S printdiff' Luca Ceresoli
2023-10-27 5:29 ` Alexander Kanavin
2023-10-27 7:43 ` Luca Ceresoli [this message]
2023-11-06 12:47 ` Richard Purdie
2023-11-06 13:07 ` Alexander Kanavin
2023-11-06 13:19 ` Richard Purdie
[not found] ` <17950980CB694D6A.12603@lists.openembedded.org>
2023-11-06 15:19 ` 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=20231027094355.1a43f67b@booty \
--to=luca.ceresoli@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--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.