From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Kristian Klausen <kristian@klausen.dk>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][honister][PATCH] cri-o: switch from master -> main
Date: Thu, 16 Dec 2021 21:44:21 -0500 [thread overview]
Message-ID: <20211217024418.GA29189@gmail.com> (raw)
In-Reply-To: <20211216120300.198575-1-kristian@klausen.dk>
Cherry-picked to honister.
Bruce
In message: [meta-virtualization][honister][PATCH] cri-o: switch from master -> main
on 16/12/2021 Kristian Klausen wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> cri-o has joined the projects switching their default branch to
> main (and removing the old one).
>
> We update our recipe to avoid fetcher errors.
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
> ---
> recipes-containers/cri-o/cri-o_git.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-containers/cri-o/cri-o_git.bb b/recipes-containers/cri-o/cri-o_git.bb
> index 41b8625..b93c3de 100644
> --- a/recipes-containers/cri-o/cri-o_git.bb
> +++ b/recipes-containers/cri-o/cri-o_git.bb
> @@ -16,7 +16,7 @@ At a high level, we expect the scope of cri-o to be restricted to the following
>
> SRCREV_cri-o = "1d447191ee73ead59f344f354edac5d64f377e15"
> SRC_URI = "\
> - git://github.com/kubernetes-sigs/cri-o.git;branch=master;name=cri-o;protocol=https \
> + git://github.com/kubernetes-sigs/cri-o.git;branch=main;name=cri-o;protocol=https \
> file://0001-Makefile-force-symlinks.patch \
> file://crio.conf \
> "
> --
> 2.34.1
>
prev parent reply other threads:[~2021-12-17 2:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 12:03 [meta-virtualization][honister][PATCH] cri-o: switch from master -> main Kristian Klausen
2021-12-17 2:44 ` Bruce Ashfield [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=20211217024418.GA29189@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=kristian@klausen.dk \
--cc=meta-virtualization@lists.yoctoproject.org \
/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.