From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>, alexis.lothore@bootlin.com
Cc: Mikko Rapeli <mikko.rapeli@linaro.org>,
Openembedded-core@lists.openembedded.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [OE-Core][PATCH v3 4/4] core-image-ptest: append ptest directory to artifacts list
Date: Thu, 15 Jun 2023 08:03:44 +0100 [thread overview]
Message-ID: <2ab334cad37a96bfa119acd45a7e760c3ba3c429.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj91ma6TFrZGsYegK6ZpQMRKudN_K6hqSW-o81MA2srntQ@mail.gmail.com>
On Sun, 2023-06-11 at 17:16 +0200, Alexander Kanavin wrote:
> Doesn't += override the earlier ?=
It depends. If ?= is parsed first, += will append. If the ?= is parsed
after +=, the ?= will not happen as the variable has a value.
> (or ??=),
+= would override ??=
Cheers,
Richard
next prev parent reply other threads:[~2023-06-15 7:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 6:47 [OE-Core][PATCH v3 0/4] add failed tests artifacts retriever alexis.lothore
2023-06-09 6:47 ` [OE-Core][PATCH v3 1/4] oeqa/core/runner: add helper to know about expected failures alexis.lothore
2023-06-09 6:48 ` [OE-Core][PATCH v3 2/4] oeqa/target/ssh: update options for SCP alexis.lothore
2023-06-09 6:48 ` [OE-Core][PATCH v3 3/4] testimage: implement test artifacts retriever for failing tests alexis.lothore
2023-06-09 6:48 ` [OE-Core][PATCH v3 4/4] core-image-ptest: append ptest directory to artifacts list alexis.lothore
2023-06-09 6:52 ` Mikko Rapeli
2023-06-09 7:24 ` Alexis Lothoré
2023-06-11 15:16 ` Alexander Kanavin
2023-06-11 15:48 ` Alex Kiernan
2023-06-15 7:03 ` Richard Purdie [this message]
2023-06-15 8:34 ` Mikko Rapeli
2023-06-15 9:05 ` Richard Purdie
2023-06-15 21:27 ` Peter Kjellerstedt
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=2ab334cad37a96bfa119acd45a7e760c3ba3c429.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=alex.kanavin@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexis.lothore@bootlin.com \
--cc=mikko.rapeli@linaro.org \
--cc=thomas.petazzoni@bootlin.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.