From: Paul Barker <paul@pbarker.dev>
To: reatmon@ti.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] u-boot: Update git server and branch
Date: Wed, 15 Jul 2026 19:45:28 +0100 [thread overview]
Message-ID: <e2046a9aa4ac8f06f084e41765fe4e8062fc849f.camel@pbarker.dev> (raw)
In-Reply-To: <20260715181725.936386-1-reatmon@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
On Wed, 2026-07-15 at 13:17 -0500, Ryan Eatmon via
lists.openembedded.org wrote:
> The u-boot project has moved to a new official git repository server [1] for
> all of their work and switch from master to main for the default branch.
>
> [1] https://git.u-boot-project.org/u-boot/u-boot/-/commit/2a6ca4ad04e64488ac41c3683cacd44173a96d24
>
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> ---
> meta/recipes-bsp/u-boot/u-boot-common.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-bsp/u-boot/u-boot-common.inc b/meta/recipes-bsp/u-boot/u-boot-common.inc
> index 574768b9f8..55f33efc98 100644
> --- a/meta/recipes-bsp/u-boot/u-boot-common.inc
> +++ b/meta/recipes-bsp/u-boot/u-boot-common.inc
> @@ -14,7 +14,7 @@ PE = "1"
> # repo during parse
> SRCREV = "88dc2788777babfd6322fa655df549a019aa1e69"
>
> -SRC_URI = "git://source.denx.de/u-boot/u-boot.git;protocol=https;branch=master;tag=v${PV}"
> +SRC_URI = "git://git.u-boot-project.org/u-boot/u-boot.git;protocol=https;branch=main;tag=v${PV}"
>
> B = "${WORKDIR}/build"
From #u-boot on irc.libera.chat today:
14:52:10 <marex> Tartarus: can we already start using the git.u-b-p.org as a primary git tree ?
14:59:18 <Tartarus> marex: My hope was to switch over officially next week. I need to see what else needs to be done before we can fully switch over
15:11:52 <marex> Tartarus: ACK
16:19:06 <bryanb> Tartarus: I noticed the commit too. should yocto people start switching things over for their CI/CD stuff as well or should they hold off?
16:19:58 <Tartarus> bryanb: Hold off a bit more
So, we should probably wait a week or two before taking this.
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2026-07-15 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 18:17 [OE-core][PATCH] u-boot: Update git server and branch Ryan Eatmon
2026-07-15 18:45 ` Paul Barker [this message]
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=e2046a9aa4ac8f06f084e41765fe4e8062fc849f.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=openembedded-core@lists.openembedded.org \
--cc=reatmon@ti.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