From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Nataliya Korovkina <malus.brandywine@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Set default CONNECTIVITY_CHECK_URIS to https://www.yoctoproject.org/
Date: Thu, 20 Feb 2020 15:27:56 +0000 [thread overview]
Message-ID: <18c55700df9ee84ea44fbffc93ba4e9f3c0e1663.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200220150318.20003-1-malus.brandywine@gmail.com>
On Thu, 2020-02-20 at 10:03 -0500, Nataliya Korovkina wrote:
> Signed-off-by: Nataliya Korovkina <malus.brandywine@gmail.com>
> ---
> meta/conf/distro/include/default-distrovars.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/conf/distro/include/default-distrovars.inc
> b/meta/conf/distro/include/default-distrovars.inc
> index 433d4b6651..6c9155b2ae 100644
> --- a/meta/conf/distro/include/default-distrovars.inc
> +++ b/meta/conf/distro/include/default-distrovars.inc
> @@ -48,4 +48,4 @@ KERNEL_IMAGETYPES ??= "${KERNEL_IMAGETYPE}"
> # fetch from the network (and warn you if not). To disable the test
> set
> # the variable to be empty.
> # Git example url: git://git.yoctoproject.org/yocto-firewall-
> test;protocol=git;rev=master
> -CONNECTIVITY_CHECK_URIS ?= "https://www.example.com/"
> +CONNECTIVITY_CHECK_URIS ?= "https://www.yoctoproject.org/"
Why would that be better?
There have been several requests to change this however I'm not sure we
can find one perfect url we can use :(
Cheers,
Richard
next prev parent reply other threads:[~2020-02-20 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 15:03 [PATCH] Set default CONNECTIVITY_CHECK_URIS to https://www.yoctoproject.org/ Nataliya Korovkina
2020-02-20 15:27 ` Richard Purdie [this message]
2020-02-20 16:30 ` Nataliya Korovkina
2020-02-20 16:36 ` Ross Burton
2020-02-20 16:52 ` Jean-Marie LEMETAYER
2020-02-20 19:29 ` Nataliya Korovkina
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=18c55700df9ee84ea44fbffc93ba4e9f3c0e1663.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=malus.brandywine@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox