From f1a39f97ac7c4e774ecfed5f4fe2824fe67984fb Mon Sep 17 00:00:00 2001 From: Pavel Zhukov <pavel.zhukov@huawei.com> Date: Thu, 16 Dec 2021 09:27:43 +0100 Subject: [PATCH] default.xml: Switch to kirkstone-next branch Default.xml still points to dunfell branch even if it's kirkstone-next now. Not changing dunfell name in comments to not cause additional conflicts on ongoing rebase Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com> --- manifests/default.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/manifests/default.xml b/manifests/default.xml index 33af03cb..c0cbe64a 100644 --- a/manifests/default.xml +++ b/manifests/default.xml @@ -33,7 +33,7 @@ SPDX-FileCopyrightText: Huawei Inc. Hence, the layers setup below uses corresponding "dunfell" layers or "dunfell" compatible revisions. --> - <default remote="oniro" revision="dunfell" sync-j="4" /> + <default remote="oniro" revision="kirkstone-next" sync-j="4" /> <!-- dunfell is using the 1.46 bitbake branch so the bitbake project follow is following this branch. More info can be found at https://wiki.yoctoproject.org/wiki/Releases. @@ -71,7 +71,7 @@ SPDX-FileCopyrightText: Huawei Inc. --> - <project name="oniro" revision="dunfell" path="oniro"> + <project name="oniro" revision="kirkstone-next" path="oniro"> <linkfile src="README.md" dest="README.md"/> </project> <project name="meta-arm-dunfell-backports" revision="dunfell" path="meta-arm-mixin" /> -- GitLab