Skip to content
Snippets Groups Projects
Commit f1a39f97 authored by Pavel Zhukov's avatar Pavel Zhukov
Browse files

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: default avatarPavel Zhukov <pavel.zhukov@huawei.com>
parent dce6227f
No related branches found
No related tags found
1 merge request!30flavours/zephyr/local.conf.sample: Bump CONF_VERSION
......@@ -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" />
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment