From: Ross Burton <ross.burton@arm.com>
To: meta-arm@lists.yoctoproject.org
Cc: nd@arm.com
Subject: [PATCH 04/10] CI: switch back to master
Date: Thu, 12 Jan 2023 11:02:51 +0000 [thread overview]
Message-ID: <20230112110257.2070363-4-ross.burton@arm.com> (raw)
In-Reply-To: <20230112110257.2070363-1-ross.burton@arm.com>
We're now compatible with oe-core master, so update the CI to build
against master branches instead of langdale.
Signed-off-by: Ross Burton <ross.burton@arm.com>
---
ci/base.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ci/base.yml b/ci/base.yml
index 7f209de1..23fb7cc7 100644
--- a/ci/base.yml
+++ b/ci/base.yml
@@ -5,7 +5,7 @@ distro: poky
defaults:
repos:
- refspec: langdale
+ refspec: master
repos:
meta-arm:
--
2.34.1
next prev parent reply other threads:[~2023-01-12 11:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 11:02 [PATCH 01/10] meta-*: mark layers as compatible with mickledore only Ross Burton
2023-01-12 11:02 ` [PATCH 02/10] arm: Add addpylib declaration Ross Burton
2023-01-12 11:02 ` [PATCH 03/10] arm-toolchain: remove obsolete oe_import Ross Burton
2023-01-12 11:02 ` Ross Burton [this message]
2023-01-12 11:02 ` [PATCH 05/10] CI: remove obsolete linux-yocto workarounds Ross Burton
2023-01-12 11:02 ` [PATCH 06/10] Revert "CI: revert a meta-clang change which breaks pixman (thus, xserver)" Ross Burton
2023-01-12 11:02 ` [PATCH 07/10] arm-bsp/fvp-base*: no need to remove rng-tools from openssh Ross Burton
2023-01-12 11:02 ` [PATCH 08/10] arm-bsp/fvp-baser-aemv8r64: Rebase u-boot patches onto v2022.10 Ross Burton
2023-01-12 11:02 ` [PATCH 09/10] arm-bsp/u-boot: corstone500: bump to 2022.10 Ross Burton
2023-01-12 11:02 ` [PATCH 10/10] arm-bsp/u-boot: Corstone1000: bump to v2022.10 Ross Burton
2023-01-12 13:31 ` [meta-arm] [PATCH 01/10] meta-*: mark layers as compatible with mickledore only Denys Dmytriyenko
2023-01-13 15:03 ` Jon Mason
2023-01-13 18:05 ` Jon Mason
2023-01-20 2:01 ` Jon Mason
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=20230112110257.2070363-4-ross.burton@arm.com \
--to=ross.burton@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nd@arm.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;
as well as URLs for NNTP newsgroup(s).